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

    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 →
  3. 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... :)

    3 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  4. PALO.DATA.AVG -> add option to count zero cells/values

    Please add an option in the function to include Zero values into the calculated average.

    Also add the option to PALO.DATA.CNT

    1 vote
    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 →
  5. 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)

    1 vote
    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. Refactor Store zero values and empty strings

    The Store zero values feature is interesting but far too extreme. One should have the possibility to refine and define the property for particular slices, not necessarily for a complete cube.

    2 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 →
  7. Built-In Scalar Dimension

    Scalar1 for instance would be a dimension with predefined values from 0-100. You could assign meaningful names to each value using an alias. The benefit would be that rules requiring a previous or next value would not require a "lookup" for what the previous or next value is. This is important in nested rules. For instance in occupational modelling where next year, next age is a function of previous year, previous age.

    NEXT_YEAR, NEXT_AGE = PALO.DATA("XXXDatabase","CCCube",PALO.EPREV("XXXDatabase","XXDimension",!'XXDimension'),PALO.EPREV("XXDatabase","YYDimension",!'YYDimension'),…) * …

    This could be replaced with NEXT_YEAR, NEXT_AGE = PALO.DATA("XXXDatabase","CCCube",PREVIOUS("XXDimension"),PREVIOUS("YYDimension"),,…) *

    1 vote
    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 →
  8. 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 →
  9. 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 →
  10. 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…

    1 vote
    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. Drill history should drill down to base level automatically

    Drill History Right now only delivers values when all dimensions are set to base Elements. So users can only see the history of a cell when all base Elements are known. That is very unlikely and is in contradiction to the usage of the flexible cube layout when only relevant Dimensions are given in PALO.DATA using PALO.EL()

    Drill History should rather work in the same way as drill thru and drill down C-Elements automatically.

    1 vote
    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 →
  12. 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

    3 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 →
  13. 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 →
  14. Make global subset definitions independent of IDs

    Global subsets are currently stored with IDs referencing elements. THis leads to broken global subsets whenever a dimension is loaded in modus update or transfered to the production environment via the new database script functionality.

    19 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 →
  15. 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 →
  16. Semi-additive measures: AverageNonEmpty, LastNonEmpty

    It is very helpful that Jedox has implemented the first semi-additive measures in version 6.
    (AVG, Last/First Child)

    It would be great if this could be continued by 2 more of them:

    1.)
    Most important would be AverageNonEmpty, to get an avarage only across children, who have a real value.

    2.)
    Another one would be LastNonEmpty, which should give you in a certain time period the last real value.

    Examples:
    .. if you monitor price changes or inventories, it should give you the last price or the last stock value for each product in a year
    (independent if this value…

    18 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 →
  17. Aggregated total of a subset via PALO.DATA

    It should be possible to get an aggregated total value across dynamic selections from the OLAP server.
    Example: get a total revenue value accross selected products matching a certain criteria.

    So it should be possible to get an aggregated total of a subset out of a single PALO.DATA formula,
    like this:

    PALO.DATA ("myDB","ProductCube",PALO.SUBSET(<filter/conditions>), ...)

    instead of only getting the value for dimension elements via:
    PALO.DATA ("myDB","ProductCube","ProductGroupA", ...)

    14 votes
    Vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. Historize consolidation factors

    A possibility to set consolidation factors depending of several dimensions would dramatically increase the slowly changing dimensions (SCD, see Kimball's bibles) management possibility of Jedox OLAP server.

    Example:
    in 2014 is my Regions hierarchy as follows:
    West
    => France
    => Germany
    => Belgium
    East
    => Poland

    in 2015 Germany will be moved in East:
    West
    => France
    => Belgium
    East
    => Poland
    => Germany

    To manage that I must have 2 different element "West" and "West-2015". That's ok for such a trivial example but when dealing with P&L hierarchy for instance that can really become very complex, especially for the…

    14 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. 91 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 →
← Previous 1 3 4
  • Don't see your idea?

Jedox Feature Voting Tool

Feedback and Knowledge Base