What is the problem or goal the end user is trying to solve or accomplish?
Preset provides multiple different time grain options for creating temporal charts (the options vary in accordance to the DB engine powering the chart).
When changing to a shorter aggregation (for example from a monthly to a daily aggregation), it's possible the chart exceeds the row limit, resulting in data missing the chart.
How are they solving it currently?
Users need to double check the row limit in the chart. When working with multiple dimensions, they might need to double check the amount of returned rows in SQL Lab to ensure the chart is not missing data.
What is the recommended solution by the Customer?
Notify the user in a more clearer way (both in the chart level and the dashboard level) when a temporal chart has reached the row limit.