Ideas

In Views, rows can be filtered by an attribute value (or Alias). However, if the user picked a Alias format (such as "Element name (Alias"), this can lead to result which might be unexpected. For example, when filtering for "start with" + some cha...

Currently the outcome leads to confusion

Currently you need to use the Advanced properties dialog to add totals to a stacked bar chart. As this is a commonly required feature it would be preferable to set this option in the main chart properties section

This functionality would be very useful for iterative calculations over the same cube rules, or for Monte Carlo scenario simulations with randomly-generated changes in specified input parameters. It could also be quite useful for AI functionality ...

A clustered and stacked chart has clusters of columns or bars, with a stack in each column or bar. Similar to the example shown below: This type of chart can be used to compare actual vs. budget by category, for example.

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

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

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.

Background: I would like to show a specific button depending on a combobox variable. If the combobox shows A, a button should be shown. (which executes 2 tasks)If the combobox shows B, another button should be shown. (which executes 3 other tasks)...

Users can select a "private" subset to use in a View for one of the view's dimensions. Since the subset is private, it's only usable for that specific user. If they would now save this View as "global" (meaning, all other users can see & open ...