When you bring up a Drill Anywhere View, make it an option to then Drill Anywhere again. This will be very powerful and allow one to drill to driver cube level.
Filter virtual dimension elements in Views / Charts
A virtual dimension always has a certain structure. - <attribute name>-- Total <attribute name>--- <attribute value>---- <base element>-- No <attribute name>--- <base element> While this is good enough for data ...
Ability to decide if a Paste View can be used as an input template or only for reporting
It would be nice to have an option to control data entry using Paste Views. Currently, Paste Views by default provide ability to enter the data (As long as user has write access). My suggestion would be to have a checkbox in Paste View option wher...
Scheduler - visualize like a calendar for a better overview
To organize the different tasks and have a good overview over open timeslots it would be helpfull to visualize each task in a calendar. (Just like organizing people in an outlook calendar or teams calendar.) One would be able to see whether a week...
Retrieve information from parent node in JSON extract
When hierarchical data is retrieved from a REST endpoint, it's really cumbersome to get that data into a dimension. Imagine, your JSON data has the following hierarchy: Legal entity > Function Area > Cost Center Naturally you'd configure you...
Attribute "Name" should be shown for multiple languages by default
In Modeler in dimension attribut e.g. "Name" should be shown for multiple languages by default or based on selection & activate search functionality. Use case: Currently as a user I need to select each time I open the dimension the Name German...
Expand column aggregation to include more than 2 column inputs
It would be great to be able to add additional columns in the Column Aggregation Transformation Function so the aggregation can be calculated based on the unique dimension elements from another column. Currently, it allows max two columns but woul...
It would be helpful if you could choose whether a CSV or Excel file should be created when exporting ETL DATA PREVIEW. As is the case when exporting drill-through data.
The setting language of the product should automatically change the report language when the translation is available
Setting of a language should automatically be recognized in the views set-up panel and pre-populate/re-select the correct element name if a translation alias is avaiable: Make the alias a variable and related to the system languages, so dimensions...