Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

Ideas

Showing 193

Distributing Jedox Suite Components on Multiple Servers

The possibility to distribute every component on multiple servers will ensure scalability for very large models. One Master could distribute read requests to multiple workers and aggregate the results from all workers before sending the result to ...
over 6 years ago in Jedox Platform / Other 1 Future Consideration

Automate environment migration (Web reports, database, security ...)

Automate by scripts or the web console, imports and exports from one environment to another (Web reports, database, security ...) without performing a restart of Jedox Setup (“Repair”)
over 6 years ago in Jedox Platform / Other 3 Future Consideration

Aggregated total of a subset via PALO.DATA

It should be possible to get an aggregated total value across dynamic selections from the OLAP server. Example: get a total revenue value accross selected products matching a certain criteria. So it should be possible to get an aggregated total o...
over 6 years ago in Jedox Platform / Other 2 Future Consideration

Request to change behaviour of LoopParallel Job

From LoopParallel Job (jedox.com) and Parallel Job (jedox.com) , "Suppose at the beginning of a parallel execution there is already another running parallel execution. In that case, the new one will only have one parallel sub-execution, i.e., no e...
about 1 year ago in Jedox Platform / Integrator 0 Future Consideration

MS Connectivity: Ensure Azure Blob Storage/Data Lake v2 Connection also works with MS Fabric/OneLake

Microsoft are heavily pushing MS Fabric and thereby their "OneLake" concept. "OneLake" can be adressed similarly to DataLake v2 and thereby probably as Blob Storage, but I think none of us have tested that. Furthermore, we don't show the wording "...
over 1 year ago in Jedox Platform / Integrator 0 Future Consideration

Fallback to default connection-database setting for Palo formulas

As a web report designer in a model I want all Palo formulas to use the system.connection and system.database model settings so that the key user of the model can easily change the database name in the settings. To achieve this today the web repor...
over 3 years ago in Jedox Platform / Jedox Web Navigation / My Models 0 Future Consideration

Increase the size of some ETL- input fields for better handling and input

Please increase the size of some ETL- input fields, where many characters can be entered.For instance: logical expression fields; json template in JSON connections, etc.The current size is error-prone and inconvenient.
almost 4 years ago in Jedox Platform / Integrator 0 Future Consideration

Dynamic header component

When creating a json extract the different column names can be defined. This would be great that it does not have to be defined manually but dynamically, I see 2 possibilities: 1/ getting the column list from another extract or transform 2/ have a...
over 4 years ago in Jedox Platform / Integrator 5 Future Consideration

Add the planning unit (for example company) as key word in emails

In the workflow emails there is no hint to the planning entity which is effected. This problematic in case of many worflow emails (e.g. as power user or regional responsible qho has to submit many planning entities). Could you please create a key ...
about 1 year ago in Jedox Platform / Other 0 Future Consideration

Provide dedicated version description fields for integrator projects and modeller objects

Currently, we use the standard description fields in integrator projects, cubes, and dimensions for 2 purposes: 1.) General information about the structure and function of the project or cube/dimension 2.) Documentation of changes (2025/03/17 John...
8 months ago in Jedox Platform / Integrator 0 Future Consideration