Preset Feature Feedback
What is the problem or goal the end user is trying to solve or accomplish?
Users need the ability to include NULL values when using a numerical range filter in dashboards. This is particularly useful when dealing with missing data that should be interpreted as "greater than the highest value" or included in filtering results.
How are they solving it currently?
Currently, Preset (Apache Superset) excludes NULL values from numerical range filters by default. NULL doesn't get reflected even applying Jinja workarounds.
What is the recommended solution by the Customer?
Modify the Numerical Range filter to provide an option for including NULL values.
Allow users to choose whether NULL values should be:
Excluded (default behavior).
Included as "greater than the highest value."
Treated as a custom value (e.g., user-defined threshold).
Ensure this functionality works across all supported databases in Preset
