What is the problem or goal the end user is trying to solve or accomplish?
Users want to ensure that the date range filter accurately reflects the actual date bounds of the underlying dataset. This prevents confusion or misinterpretation when stakeholders assume data exists for dates that are outside the actual range.
How are they solving it currently?
Currently, users can select any date range, even if it's outside the bounds of the data. This leads to misleading charts or filters with no effect, causing confusion. Users must manually verify the date coverage of the dataset and then communicate it separately to stakeholders.
What is the recommended solution by the Customer?
The customer suggests either:
Automatically limiting the date range filter to only allow dates present in the dataset.
Or at minimum, displaying a warning if a user selects a date range that falls outside of the dataset’s actual date range.