Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

All ideas

Showing 1400

Adding the option to use variables in the rows and columns of dynatables

this would enable dynatables to be driven by comboboxes, and charts in canvas to respond to combobox changes, hugely improving the useability of dynatables and charts in canvas
7 months ago in Jedox Platform / Canvas 3 Future Consideration

In DynaRanges open and colaps hierarchy levels using buttons L1 L2 L3 L4 ... LN

In DynaRanges open and colaps hierarchy levels using buttons L1 L2 L3 L4 ... LN. Just like in Modeler.
over 1 year ago in Jedox Platform / Web Spreadsheet 0 Future Consideration

Align acceptable characters across the platform

There is documentation on what acceptable characters are in Jedox web, Integrator, OLAP. However, this is not enforced by the interface. The Interface should only accept characters that the whole platform can use and enforce these rules.
over 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

Maps integration

For dashboards and data visualisation, our customers are using maps (google, ESRI, OpenStreetMap, etc) as data visualisation tools. For example, if you have a store, and customer dimension, you could have Latitude-longitude attributes, based on wh...
about 2 years ago in Jedox Platform / Canvas / Charting & Visualization 2 Future Consideration

Export a web report to Excel through dimension (bursting)

The result is an Excel with as many sheets than elements in the dimension. It allows to get reports split by channel or Customer or product without creating views manually.
over 3 years ago in Jedox Platform / Microsoft Office integrations (Excel, PowerPoint, & Word) 0 Future Consideration

Aggregate lists of elements for each dimension in PALO.DATA functions instead of single.

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,
over 6 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Rule Editor usability/GUI - grouping in folders

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...
over 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

Additional argument in PALO.DATA function to omit hashtag (#) sign for data splashing

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.
over 6 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Native Canvas Input Field

I think it would be very helpful if a native input field was created and added to the list of native canvas components. My vision for this would be a input field you could drag into a canvas which the end user could type into. This input would be ...
12 months ago in Jedox Platform / Canvas 6 Future Consideration

Custom input / "expression" as source for Canvas KPI Card

Currently, a Canvas KPI Card only accepts a specific cube cell as data source (with the ability to multi-select some dimension elements and then use average, min, or max, like in a View). This implies that all data to be shown on a KPI Card must b...
almost 2 years ago in Jedox Platform / Canvas 0 Future Consideration