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. 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
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  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.

    3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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 :)

    3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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.

    3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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…

    3 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 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
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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.

    7 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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

    6 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 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.

    15 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Allow multiple consolidation of an element

    sometimes you have to be able to consolidate the same element multiple times, for instance with consolidation factor=0 (for instance when you built a hierarchy tailor-made for a report, and you want empty rows for presentation purposes)

    9 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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)

    6 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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…)
  14. 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…)
  15. 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…)
  16. 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).

    7 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. 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.

    10 votes
    Vote
    Sign in
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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…)
  19. 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…)
  20. 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…)
← Previous 1 3
  • Don't see your idea?

Jedox Feature Voting Tool

Feedback and Knowledge Base