Range filter default values

Apps (Frontend) Apps Builder
1

Hey Community!

I am currently using a filter element like this:

{
  "id": "range_filter",
  "source": "/path/to/file.source",
  "config": {
    "column": "numerical_column",
    "label": "Value Range",
    "columnType": "DOUBLE",
    "rangeFilter": true
  }
}

Displaying this element without applying it anywhere it seems like the element defaults to the min and max values of the data defined above:
range_filter_minmax_default

However, applied inside the dataOptions/transformations of a datasource like this:

{
          "type": "filter",
          "config": {
            "column": "numerical_column",
            "columnType": "DOUBLE",
            "range": {
              "min": 0,
              "$min": {
                "type": "double",
                "value": "{{filters.range_filter.numerical_column.valueRange.min}}"
              },
              "max": 50000,
              "$max": {
                "type": "double",
                "value": "{{filters.range_filter.numerical_column.valueRange.max}}"
              }
            }
          }
        }

It changes the fields of the filter to display default values like this:
range_filter_minmax

And I get an error message saying:

"Variable 'transformations' has an invalid value: Expected type 'Float' but was 'String'.

Which also prevents the source it is applied to from loading.
Manually typing in values at this point then filter the source like they are supposed to.

Is there a way to make the filter values default to the min and max of the data like in the first image, even when applied to the source? Alternatively, is it possible to manually set default values for a range filter like this?

2

I assume that the filter element behaves similar to the table column filter where concrete values appear when “distinctValues” is enabled on the datasource and “Min” - “Max” appears when it is disabled:

"filterOptions": {
      "enabled": true,
      "distinctValues": true
    }
3

These settings are already enabled in the scenario of the initial post

4

Update: Using a copy of the data as the source in the filter definition results in the numerical values being displayed in the filter boxes by default, but the error message stays the same. So the theory of “min” and “max” being passed as strings as the cause of the problem does not seem to be the issue here.