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

    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 →
  4. Add support for IPv6

    It should be possible to use IPv6 to access OLAP server. Support includes functionality in OLAP Server and Client libraries. #15409

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

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

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

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

    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 →
  15. 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
    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. PALO.DATA.MEDIAN

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

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

Jedox Feature Voting Tool

Feedback and Knowledge Base