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

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

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

    We’ll send you updates on this idea

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

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

    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 →
  8. 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 →
  9. 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 →
  10. 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
    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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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.

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

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

Feedback and Knowledge Base