Keep the button properties (background, font) when clicking on it (web and Canvas)
I'd like it if, when the user clicks on a button, that same button could keep its properties (background, font, etc.) and not be displayed again by default. A bit like checkboxes that keep the tick displayed when you click on them.
The proposed Unified Scenario Manager aims to streamline data management by enabling seamless copying between versions and facilitating scenario creation, enhancing efficiency and flexibility. Current challenges include fragmented data copy proces...
Charts: Colour codes, fill/border, line formats and positioning should be dynamic
All colour codes, fill/border, line formats and positioning on charts should be able to be passed in from a range, named range or variable. This would essentially bring a basic "conditional" formatting to charts and cover the main things the users...
Show cube dimensions under cube in navigation pane hierarchy
Whit large implementations, where many hierarchies and cubes exists, a lot of time is spent on finding and scrolling to the hierarchies related to the cube being worked on. Although the forward and back buttons help a lot, it would also be great t...
Numeric Day and Month Value attribute in Time dimension
In a time dimension, there are month and day value attributes, which are super helpful for retrieving a date range with an attribute filter etc. However, these are currently strings and therefore may not work with some comparisons and mathematical...
The suggestion is to add the following two languages as supported by Jedox Web: Polish (pl-PL) Slovak (sk_SK) This should allow the user to change the language of the UI - Jedox Web as well as to use it to translate elements/attributes/reporting i...
Actions: put green circle to indicate actions usage
Currently it's not indicative whether there are some actions used in button, combobox, checkbox. Just for quick indication it would be nice to see green circle near Actions tab to indicate that some action is used.
Cube-to-Cube drillthrough would allow cubes to be linked logically for users and assist in data discovery. The drillthrough would use the shared dimensions for a particular drillthrough intersection to create a view on the destination cube.
This would be helpful to enable setting the target fields in a cube extract. When copying a slice to another one, I use a cube extract, then a fieldtransform where I put a constant. We could cut the FieldTransform if the target structure could be ...