Ideas

Description: Many customers create reports and dashboards for similar use cases, often starting from scratch. Instead of manually designing reports every time, AI could analyze existing customer reports and dashboards (without exposing sensitive d...

We need to enhance the Time editor to allow a 4,4,5 weeks/period time dimension. There is a common business cycle that leverages 4,4,5 weeks over the 52 weeks of the year. So, period 1 is 4-week, period 2 is 4 weeks, and period 3 is 5 weeks. This ...

More and more clients seem to be leveraging Google sheets instead of Excel. Anaplan is pursuing this strongly, and we need to consider making this an option as well.

Allow users to upload PDF documents into Jedox’s AI chat function. The system would process the uploaded PDFs to extract relevant information for analysis. Users could ask specific questions about the content or incorporate it into broader data ev...

Currently one has to create a conditional formatting to implement alternating row colors. As soon as rows are dynamically hidden or extended (e.g. drill-down in DynaRange), the alternating row colors are broken. Just like the frame of the DynaRang...

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...

The emerging trend of content-specific chatbots has the potential to significantly boost the usage of the Jedox knowledge base. By simply uploading relevant documents, you can fine-tune an existing LLM model to focus on specific topics. If the kno...

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,

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...

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 #.