Jedox Feature Voting Tool

Dear Jedox User,

in our continuous strive to improve our services, features and to help you gain your share of this ever growing market we are introducing the Jedox Feature Voting System.
This new service is currently exclusively available for you, our Users and Partners.

What is this Jedox Feature Voting System?
It is a tool that provides you with the options to create and vote on Feature request, Ideas and any other general Feedback.
This in return provides us with the necessary Information to react and provide you with the things you need.

We invite you to browse this Page, create and vote on new Features, Ideas and requests!

How can we improve Jedox Software?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Materialized Rules / Persisted Rules - for Performance Optimization (like materialized views)

    Currently rules are calculated in the moment when the user queries the data.

    It would be great to have the option to shift the timing to the point when the user changes data. So the result of the calculation would be stored/persisted when the user changes a certain parameter.
    -> in this moment the change would only affect tiny slices of the cube,
    related to the parameters of the calculation. (a bit like a SVS routine)

    Generaly this could help to optimize performance in scenarios where reporting performance is critical but data entry performance not that much.

    In relational databases…

    4 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 #.

    20 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  3. 96 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  4. 20 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Jedox Feature Voting Tool

Feedback and Knowledge Base