Preset Feature Feedback
What is the problem or goal the end user is trying to solve or accomplish?
Customer wants to display filter values differently from the actual underlying values. For instance, we could display value in Chinese, but the underlying data in table is in English
How are they solving it currently?
There's only one value used for both display and filtering.
In general I think superset needs to make filters more of a first class citizen so it'd be good for preset and the community to prioritize. I like the simplicity of virtual datasets, but sometimes querying the entire dataset to create a filter that has 3 options is a bit overkill. A simple static filter would allow for this feature, but ultimately we need to say dataset.columnA can be found by querying dataset.columnAFilter ... creates links between datasets, but seems like the most reasonable way to code it. if a dataset has a special column like __dispalyvalue or has metadata to describe it as a display value then you could have translations, shortened values, or better yet show "Name" to the user, but pass "name_id" to the underlying query.