Optimization of selection functionalities

Dominik Borchert
Dominik Borchert Customer
25 Up Votes Second Anniversary First Comment Photogenic
edited October 2021 in Idea Exchange
Hello community,

here are a few points/functionalities that could improve selection functionalities in board:
  • Allow flexible ranges in screen selection
    At the moment there is no way for a "native" range selection of a screen. If you would like to work with a range you alway need to select individually entities (using cube selections or custom time entities). The only time range that is possible is the dynamic year to date (starting from January). A dynamic "from - to" - selection that can also handle offsets would be very help.  We need the last finalized 12 months as an example quite often -> from = "actual month -13" and to = "actual month -1". In our current solution we are using custom time entities (to flag these months) that are updated every day with an ETL...

  • Allow dynamic time selections in layout selections
    It is currently not possible to use a dynamic time selection in a layout -to-selection (e.g. one chart is supposed to show the complete actual year, but screen selction selects only current month for the other objects on screen). At the moment we are using custom time entities to solve this, but these entities are limited in board. To allow a dynamic seletion in layout object as it is possible in a screen selection would be very helpful.

  • Have different time selectors on one screen that refer to one object on the screen
    At the moment the selectors affect always the complete screen. Different time selections in a layout object are implemented with a static to-selection using custom-entities. If you could link a selector to just one specfic object on the screen, that would be very helpful and would reduce the workarounds...

Thanks in advance and best regards, Dominik Borchert
7
7 votes

Archived · Last Updated