Allow runtime properties on the data source itself, not only on data source objects

Bugs and feature requests Feature requests
1

This feature request is somehow related to App Variables need some love, as many of my App Variables handle things that could have been stored directly in the data source itself. This includes items like filter-based counters and boolean variables used for logic related to the data in the data source. If I could add runtime attributes directly to the data source, I could likely keep my App Variables list much shorter.

2

Hi!

Your feedback is much appreciated and will be taken into consideration. We are aware that App Variables can become a bit unmanageable in large applications. Below we suggest an approach that we have implemented in several solutions to alleviate this challenge:

  1. Make a new object class and call it, e.g., “Runtime Variables”, if you only have one app you can scope this object class to keep your data model tidy.

  2. Add the new object class as a Data Source and make it Cardinality: One, Runtime Only and Auto Create: true. Name the data source according to what kind of variables it should hold, e.g., based on a View: “Runtime Variables: Dashboard” or an object class: “Runtime Variables: Projects”
    image

  3. Add runtime properties to your newly created data source to store your variables.
    image

  4. Repeat step 2 and 3 when you need to store variables for other purposes, to keep your variables organized:
    image

3 Likes
3

Why didn’t you tell me about this trick years ago? :wink:
But I still think search in default App Variable and runtime properties on the data source itself could speed things up and make the data model cleaner.

1 Like