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. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    6 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    10 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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).

    11 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    12 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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", ...)

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

    17 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Loging of IP Adress within SVS

    Possibilty to log the IP from each login attempt (web or excel).
    This can be helpfull in some security related problems.

    1 vote
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 #.

    19 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Dynamic Time Series

    Possibility of evaluating and YTD MTD data without appropriate hierarchy. This is relevant for evaluations of daily data.

    13 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  14. "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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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…

    15 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Jedox In-Memory Database (OLAP)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Offer a data filter for sorting

    n other tools there is beside data filter definition for the values a seperate definition for sorting.
    For what purpose?

    There is a sales report for example with two columns (Year 1, Year 2)
    and several rows (Items).
    In data filter for values you define Year1 and Year2.
    If you want to get items sorted for Year1, the only way in Jedox is to do it in datafilter. But then you will miss those items, wich have only values in Year2, but not in Year1.
    With a seperate data filter for sorting you won't loose them.
    This is good practice.

    15 votes
    Vote
    Sign in
    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