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?

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

    6 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Standard or Default Element for Splashing

    It would be nice to be able to define an element in an hierarchy as standard element. This would mean that when splashing on the parent the full value would be written on this element rather than splashed onto all the underlying elements. This would save a lot of space in the cube and avoid having to always drill down to base level to input a value.

    For example for a quick forecast I would like to forecast sales but do not want to forecast for every single product. I would like to be able to define a fallback item…

    6 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Offline Planning and Analysis Capabilities

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

    6 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Splashing with integer values

    plashing with integer values: entering integer value as splashing value, and rounding all base values to integers too(scale it according to current value) should be possible. #13541

    6 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    5 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  6. 5 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    5 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    4 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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)

    4 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    4 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  11. 4 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 and not stored and a rule is immediatly overruling the entered value and showing the rule value (e.g. rule = 100, enter 500, cells still Shows 100)

    3 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →

    We are currently working on several features which will allow report formats and styles to be driven by database content.
    The fact whether a value is rule-calculated or not will be of the database contents (or states) that we consider for driving such database-based formatting.

  13. Inverse rule like in SAC

    in SAC there is the possibility to create such a rule:

    [Marketing Cost] = [Revenue] * [Marketing Cost % of Revenue] | INVERSE ( [Marketing Cost % of Revenue] := [Marketing Cost] / [Revenue] )

    it allows you making Marketing Cost % of Revenue and Marketing Cost as well as an input (and "holding" Revenue constant)

    this in jedox is now only possible using SupervisionServer. This would be really helpful if this could be a standard feature

    3 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 :)

    3 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    3 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    3 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Show database name in "delete database" dialogue

    As the description says. At the moment, "do you want to delete this database" is asked. Just add the database name so the user knows that they haven't misclicked.
    Asking this for a friend... :)

    2 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Have BC rules: C for time dimension and B for other dimension (rules for semi-additive measures)

    Mixture of B and C rules (basically a B rule, but not for dimensions marked for semi-additive measures). => To allow rule transformations for semi-additive measures

    --- cite ---

    It would be great to define rules, which are C-rule related to the time dimension but at the same time B-rule to all other dimensions in the cube.
    (So we target consolidated elements in time dimension and base elements in all other dimensions)

    With this we could define advanced semi-additive aggregation behaviour, which is currently not provided by Jedox (e.g. NonEmptyAverage)

    Right now we only have some basic semi-additive aggregation in…

    2 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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…

    2 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Reverse Algorithm in Top down planning like excel solver

    A reverse algorithm that extends the capability to propagate changes across dimensions and hierarchies to the calculated fields (e.g. If you change a percentage value, the change will be automatically reflected in the quantities from which the percentage has been generated, even if the percentage is a calculated value) just like the solver addin in excel

    2 votes
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base