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!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    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 →
  2. consolidated element children as rule targets (targeting all child elements)

    It would be great to set a consolidated element as rule target
    in a specific mode, where the rule is targeting all child elements.

    Example:

    ['ProductGroup A'] = ...

    is then addressing

    Produkt A1
    Produkt A2
    Produkt A3
    ..

    which are all members of ['ProductGroup A'].

    -> so the rule would affect all single products instead of the product group (cons. element) itself.

    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 →
  3. 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…

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

    We’ll send you updates on this idea

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

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

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

    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 →
  7. excel F4 repeat last operation did not work

    As Jedox systems gets more and more complex, instead multiple RGP, and FGP, Config databases, a single database could be used so store all metadata about jedox.

    This help backup/restore of the system, it also might help moving development between dev/test/live systems.
    This is currently not supported in any way.

    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 →
  8. Improved RULE Debugging

    1. With a Parse Error in RULE you get an errormessage referring to a position number in the rule's string. But the editor never displayes the current position as a number, which would help locate the error.
    Or highlight the error position!

    E.g: unexpected element_string at position 108 of line 1.
    Where is position 108 exactly? Don't want to count manually.

    2. If an element is UNEXPECTED give us the EXPECTED input.

    E.g. a simple mistake like not putting strings into quotation marks blocks the whole rule. The "" could be shown as expected.

    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 →
  9. Define/bind RULES not only to cubes but also to DIMENSIONS

    Rules are often applied mainly related to the MEASURE-dimension.

    Example: 1. turnover = price x units, 2. yield = profit/turnover x 100

    If the measure-dimension is used in more than one cube then rules have to always be copied and maintained in each single cube.
    Better to bind rules directly to the dimension which simplifies development and maintenance.

    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 →
  10. Splashing for string elements delete command

    It would be great to have beside the already implemented possibility to copy string elements to delete strings on an aggregated cell.

    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 →
  11. Rule Template for version-dependant planning time frame

    Dear Jedox team,

    currently there are some templates for version dependant rules available (esp. version blending for actuals)

    It would be great to have some more potential for optimization and flexibility in this regards
    ->e.g.generation of time-frame-specific rules.

    Imagine you have several different planning versions in you version dimension - each with a different planning time frame (accross more than one year).
    It would be great to generate planning rules limited to specific time slices.

    example

    Version Dimension

    FC
    Plan2019
    Plan2020
    Plan2021

    Version Plan2019
    --> planning from 2019-06 to 2021-12
    ['Version':'Plan2019','Months':{2019-06, .., 2019-12, 2020-01, .., 2020-12, 2021-01, .. ,2021-12}] =…

    1 vote
    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. Rule template on System dimensions

    Allow queries on System dimensions, for instance #_GROUP_, to be able to define dynamic right rules (e.g. in #_GROUP_CELL_DATA_<cube>)

    1 vote
    Sign in Sign in with Jedox AG
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    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 →
  14. 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
    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 →
  15. Extend DB Script generation (cube+related dimensions, select multiple db objects)

    The option to generate DB scripts is really great!
    But currently you can only create scripts for single db objects (dimensions, cubes) or for the whole db in total.

    It would be great if Jedox would offer some options to save time.

    1.
    when I create a db script for a cube, I would need the option to
    also create scripts for the related dimensions

    2.
    in general it would be great if I could select multiple cubes and/or dimensions from a list to generate the scripts for them

    Thanks

    1 vote
    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. Attributes / Flags for Rules

    Hi Jedox team,

    currently we only have a comment section to add additional information to a rule.
    But especially for automated processing of rules via ETL it would be great to be able to mark/flag certain rules in a more structured way.

    In the first step just one additional field would be enough.
    (name could be "Tag")

    Maybe later it could be extended to something similar to the attributes for dimension elements.

    1 vote
    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. Rule Editor: Better handling to test and optimize rules

    For testing purposes

    1. A performance profiling for each rule should be possible: to track the time-consumption

    2. In the Rule Editor it should be possible to activate/deactivate a selection of multiple rules at once.

    1 vote
    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 →
  18. "Technical name"

    The technical name I would have liked in column A and not the right of the data table. Once the query is processed (e.g. adding further elements and Jedox PALO.DATAC or pasting Excel formula (comparison / VLOOKUP), there is the column with technical name " between " the data areas or the technical name is moved manually.
    Ability to display the Alias and technical names on option selection.

    1 vote
    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. Copy-Add Splashing

    I don't know if it's possible but it would be great to have a splash command which copy the value from a source that add the values in the target instead of deleting the old ones. Something like "## copy".

    1 vote
    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 →
  20. PALO.DATA.MEDIAN

    A function palo.data.median function could be useful.
    Median() Excel function is limited to 30 values.

    1 vote
    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 →
  • Don't see your idea?

Feedback and Knowledge Base