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. PALO.EPARENT and PALO.ELEVEL relative to specific root element (parallel hierarchies)

    PALO.EPARENT and PALO.ELEVEL work well if you have only 1 hierarchy within a dimension.

    But if you have more than one hierarchy it would be great to give a certain root element as parameter and get the parent and or the level in exactly this specific tree.

    13 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Show the progress of a database save operation

    A database save on a large database can take hours and uses up the OLAP process completely, i.e. you can't perform other operations while the database save is running. At the moment it is also not possible to monitor the progress of such a database save operation. It would be great to be able to monitor the progress, so that you know whether you have to wait another 3 hours (after you've already waited 3 hours) or it's done in 5 minutes.

    12 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 →
  3. Add rule function to test if an element is an ancestor of another (return boolean)

    This is helpful with large/deep hierarchies to establish relationships within rules

    11 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 →
  4. Offline Planning and Analysis Capabilities

    Add feature for users to plan or analyze an item offline.

    11 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow multiple consolidation of an element

    sometimes you have to be able to consolidate the same element multiple times, for instance with consolidation factor=0 (for instance when you built a hierarchy tailor-made for a report, and you want empty rows for presentation purposes)

    11 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 →
  6. Correct hierarchical sorting when using several groups

    when using several groups allocated to a user that have different access rights on elements of a hierarchy, the dimensions elements will not be rendered properly (e.g. show base elements as consolidated ones)

    the underlying problem is that the hierarchical sorting in Subset does not work in combination with user rights.

    This is quite confusing for the users. This would be really awesome if this problem could be corrected

    @jedox team: support ticket #2019012178001116

    10 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  7. audit trail without time limitation

    The Audit trail is a often requested feature and implemented quite well. Only drawback is the limited duration auf trail. Why is there a maximum of 30 days? The ressources of the server should be the limit.

    10 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 →
  8. 10 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 →
  9. 8 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 →
  10. Switch to include PALO.EL with Paste Data Function

    To make use of the new flexible cube layout functionality PALO.EL subfunctions inside the PALO.DATA are needed. Inserting the PALO.DATA with the "Paste Data Function" dialogue thus requires to manually edit this pasted function for each dimension of the cube. It would be nice to have a checkbox or similar in the "Paste Data Function" dialogue to call for automatically inserted PALO.EL subfunctions (either with the default element as chosen by "guess arguments" or the default read element if specified, not sure which would be better).

    8 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 →
  11. Hide specific dimension elements to reporting user

    Sometimes we create some elements just as helpers for certain calculations or tricks (kind of dummy elements) .. those helper elements are not intended to be used for reporting.
    Therefore it would be great to be able to mark them as invisible,
    so that they do not appear in paste view dialogs or insert element dialogs or similar.

    thanks :)

    7 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  12. 7 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Enable Audit logging option for "14days"

    Currently there is only the option of choosing 1,7 30 or 365 days of audit logging. Our customers that are interested in this functionality want the options of 14 days, as 1 week simply might not be enough time to catch a mistake. On the other hand, 30 days is too much. This should be simple to implement as it is just between the 7 days and 30 days options.

    7 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 →
  14. show explicit right when inherited

    in #_GROUP_DIMENSION_<dim name> cube this is really complex to know what is the right for a certain group since it can be inherited from upper levels, for instance:

    Europe N
    West <empty>
    France R

    this would be great to be able to see that, say using a "flag" to state the inheritance:

    Europe N
    West N (inherited from Europe)
    France R

    6 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 →
  15. Audit feature to save previous value

    Audit feature that allows you to see the cell value before splashing (only C-level, not all the details on N-level). Now you can only see the new value.

    6 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 →
  16. Substitute #VALUE errors from missing rights by 0

    If a user is restricted by #_GROUP_DIMENSION_DATA_* to a specific area he will usually get a #VALUE error for everything else (in Web as well as Excel). Sometimes it would be more beneficial to treat these #VALUE errors as 0s, so that the user experience is the same as if they would have access to all data (hierarchies etc.) but only their data is stored in the cube and everything else is 0.

    You might wonder where this comes in handy - imagine a Cost Center Hierarchy of several hundred cost centers that are arranged productwise while peoples responsibilities are…

    6 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 →
  17. Independent rights on database level

    Abstract:

    User rights on OLAP objects in a database should not be influenced by user groups that are disabled for this database.

    Case:

    As you probably know one can limit user rights to certain databases via cube System/#_GROUP_DATABASE_DATA. A user with a restricted group is then only able to access data from this particular database.

    Additionally one can combine this database permission with e.g. dimension restrictions (via #_GROUP_DIMENSION_DATA_*) so that the user can only see specific elements e.g. reports by making use also of #_CONFIGURATION option HideElements set to "Y".

    The problem:

    Let's further assume that you have two databases…

    6 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  18. new clause in jedox db scripts "create if not exists"

    Currently the standard option "ERROR_IF_EXISTS" is not convenient for instance to update a dimension on a prod machine from a dev machine.

    this clause is also standard in databases dumps (e.g. CREATE INDEX "myIndex" IF NOT EXISTS)

    6 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 →
  19. Creation/update timestamp for common objects

    This would be great to have a creation or update timestamp for common objects (like it is the case for rules for instance)

    This would allow to know better what has to be migrated from a server to another for instance

    4 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 →
  20. 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 →
  • Don't see your idea?

Jedox Feature Voting Tool

Feedback and Knowledge Base