Reader Drill Up/Down of Timestamps in a a table.... Option Gone?

I have a dashboard that is very simple.

It is a direct query to a table in a Snowflake data warehouse that just loads Timestamps rounded to the nearest 5 minutes and a count of the number of times a certain action happened during each block of time.

I have table visualization set up. The Readers on the dashboard used to be able to click on the timestamp and drill up to hour, day, etc. This functionality has now disappeared from the dashboard… Now they cannot…

Why was this functionality changed? The data itself is not different, I didn’t change the dasbhoard, just the option is not there. This appears to have happened sometime in the last week.

here is another post that talks about the exact functionality I am trying to bring back to my dashboard. The drill down/Up function is selected in the publishing options. I republished it and double checked that that that option was selected, but still cannot drill up or down.

1 Like

@TRube ,

I will check this at my end. In the meanwhile, would you able to open a support ticket at your end for the team debug this further ?

Here are the steps for opening a support ticket - Creating support cases and case management - AWS Support . If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf

Kind regards,
Koushik

2 Likes

I will do that, thank you.

This is the response I got from AWS. Honestly, this is pretty disappointing. IMO, AWS’s support of Quicksight is pretty amateur compared to PowerBI. This could break dozens of dashboards for people, and telling them to make new dashboards is the worst possible solution.

*I understand that the drill-down feature for date fields in your dashboard is currently not functioning as expected. Users are only seeing the “Focus Only On” option when clicking a timestamp, which is understandably frustrating. This issue began approximately two weeks ago and is affecting multiple dashboards that previously supported drill-down capabilities. To address this, I have taken several steps. *

*Based on feedback from our internal team and community resources, it appears that the drill-down functionality is an expected behavior for date fields in tables has unfortunately been impacted by a bug. This change was made due to previous issues where the feature did not function correctly and only altered the aggregation without providing true drill-down capabilities. *

*Our team is actively working on a release to address this bug. However, please note that there are currently no plans to restore the drill-down feature for tables to its previous state. In light of this situation, I would like to offer some recommendations to help you navigate the changes. Although the drill-down functionality may not be re-enabled, users can still change the aggregation type for date fields (e.g., year, quarter, month) directly from the field well. I suggest sharing this capability with your team to ease any frustrations. If drill-down is essential for your analysis, consider utilizing visualizations like charts that continue to support this feature. *

Transitioning to these visuals can help maintain the insights you need. Additionally, if necessary, creating new dashboards or visuals can ensure access to the required data insights. I recommend informing end-users about this change in functionality, providing them guidance on how to adjust aggregations in tables and encouraging the use of chart visualizations for drill-down capabilities. Please stay tuned for any new updates from AWS regarding any enhancements or fixes that may restore desired functionalities in future releases. I also encourage users to share their feedback with the QuickSight community or your internal team about their needs for drill-down features. This feedback can be invaluable in prioritizing enhancements in our product roadmap.

Hi @TRube,
I agree that this is not an ideal solution for this type of situation. I’ll mark this as a feature request to promote additional updates to assist in this type of scenario.

If you have any additional questions or comments, feel free to create a new topic in the community and link this discussion for relevant information if needed.

Thank you!