Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 127

In a cube with persisted relational ETL drillthrough data, allow cube-drilldown in areas where no relational data is available.

As of version 2023.4, the Jedox drillthrough capabilities have become a native functionality outside of the SVS scripts. In the KB it says for the mode automatic: drills through if ETL is available, or else drills down. This suggest that right-cli...
11 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Transpose (interchange) rows and columns in the dimension editor of the Modeler

Some dimension have more attributes then elements. In these cases it would help to transpose/ interchange between columns & rows in order to make more values fit on one page. Having e.g. all values on one screen would help to get a faster &...
almost 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Expand Default value of attributes to further components of the Jedox plattform

The functionality to set Default values for dimension element attributes (currently available in the Modeler) should be also available a) when uploading a dimension from a file with the Modeler, b) when loading a dimension with Integrator, c) ...
almost 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Expand Domain constraints for attributes to further components of the Jedox plattform

The functionality to constraint attribute values via a Domain (currently available in the Modeler) should be also available a) when uploading a dimension from a file with the Modeler, b) when loading a dimension with Integrator, c) when enteri...
almost 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Use Version Type instead of Version Name for Rule Template KPI calculation (by Version)

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, section KPI calculation (by Version), there was a note that "for this query type, the version dimension must have the specific name "Version". This naming requ...
almost 2 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

In Modeller group databases by model to which they belong.

In Modeler we often have many databases with different names. In our situation, we have several teams working on separate projects.Most projects are grouped via Models functionality where the Model groups Reports, Integrator jobs, and Scheduler ta...
12 months ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 0 Future Consideration

PALO.DATA.SOURCE Identify Rule-based values/cells

PALO.DATA.SOURCE Identify rule-based values/cells Function to identify, if a value is calculated or stored in the database. This enables dynamic reports where a conditional formatting opens cells for data entry ONLY if they are actually stored an...
about 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Microsoft Office integrations (Excel, PowerPoint, & Word) 1 Future Consideration

Keep full trace in audit trail.

When planning functions such as splashing or copy are used, the audit trail does not keep a complete record of what has been entered. For example, executing the following command “copy Actual;2023” only records the following NUMERIC_VALUE: 12345,...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

LET Function in rules

a LET function would be really helpful in the rules, especially for complex ones.
over 4 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Allow Cloud Backups without downtime

Some components of Jedox need to be shut down to perform the daily backups. During this time the environment cannot be used. This is problematic for companies that are working around the globe during all 24 hours.
over 3 years ago in Jedox Platform / In-Memory DB / Jedox Cloud 0 Future Consideration