All ideas

Toggling between aggregated and raw-records in the table chart doesn't keep metrics and dimensions. Dimesions should translate to Columns when changing from aggregate to raw.

Preset documentation is very limited, which makes it hard to know how to successfully implement Preset, best practices to adopt, and solutions to follow (how to show YoY). They wished to learn about other companies use cases and experiences.

Builders (of charts and dashboards) would like to empower the viewers (of charts and dashboard) to explore chart content by allowing them to apply a different dimension(s). These dimensions are available in the dataset and the desired interaction ...

What is the problem or goal the end user is trying to solve or accomplish? Users would like to perform time comparison calculations on the Calendar Heatmap chart, to indicate how a metric varies daily when compared to a previous period. How are th...

In the Explore interface, implement filters that are relient on one another. Set one filter and on applying the next filter, limit the options to only the sub-categories of the previous filter. Example: setting a filter for Region (eg North Americ...

What is the problem or goal the end user is trying to solve or accomplish? A feature that allows to gather feedback on the usefulness of a published dashboard How are they solving it currently? Not Achievable through Preset at the moment W...

What is the problem or goal the end user is trying to solve or accomplish? Users would like to easily indicate if their values are higher/lower than a previous period by conditionally setting colors (for example red for number below previous perio...

Users get confused and disoriented when their expected action/flow can no longer be performed due to product changes. They would like to be notified about such changes, so they can quickly perform their action.

A user would like the SQL Editor to provide the option of creating a table/view directly at the data source level (e.g., Athena). This would help improve the process of having to work with one query at a time.

What is the problem or goal the end user is trying to solve or accomplish? User is looking at doing table calculation to calculate the percentage eg: Data: User_ID Event 1 Unlocks Door 1 Opens Door 1 Closes Door 1 Locks Door 2 Unlocks Door 2 Opens...