QuickSight Actions

Hi Team,

I have a question about QuickSight action. I have a QuickSight view that consists of two visuals: 1. a pivot table, and 2. a table.

The table is my detailed view where I’m showing my data at its lowest level of granularity (PK: anchor_Date, ISA) and shows dimensions such as warehouse_id, status, check-in date, is_reactive, is_cut_compliance, is_past_due, etc. In my pivot table, I have anchor_date as the column, site as the row, and a bunch of metrics (all calculated columns) that are essentially counting the number of ISAs based on different statuses.

I created an action between the two visuals, and I’m hoping that by clicking on the numbers in the pivot table, my detailed view table gets filtered. For example, if my pivot table shows that warehouse ABC1 on 10/15 has 5 compliance trailers, clicking on 5 should give me the list of 5 ISAs in the detailed view.

I’ve been a Tableau user for years, and something like this doesn’t need a data setup since both tables are reading from the same data source. But for some reason, I’m unable to build this interaction between the two datasets. I’d like to get experts’ opinions as to why this interaction doesn’t function the way I expect it to work. Thanks!

This feature is not readily available as in Tableau. Have you tried to configure the drilldown action setting?

@kanakatv Thanks for your response. Would you mind elaborating more on “what drilldown action setting” is?

Hi @nebadi

I think the Filter action should be able to do the filtering, but it appears there are some nuances to how the two visuals work together.

The filtering columns between the two data sets should have the same name and data type.

See my example below

I have two datasets and I have added two visualizations to my analysis one from each of the datasets. When I initially created the Filter action no fields were mapped between the two datasets. Then when I read the documentation it says that the field mappings are done automatically and that you need the names of the columns to be same and their data types to be same.

In my second dataset I had the column for date with a different name and I created a calculated field using my date column and named it similar to my first dataset. I then re-created the filter action again and as you can see the field is now mapped!

So, for the two columns that you want to link with the second visual you will have to do the same and it should work!

@nebadi Mocked up a sample of your dataset and here are the steps to implement the drilldown action on it -

  1. Click on the 3 dots on the summary table and select ‘Actions’.
  2. On the pop-up that appears for Actions, select the option ‘Filter same-sheet visuals’ and that will create a drilldown action similar to Tableau.
    image
  3. In case you like to apply the drilldown action to only few selected visuals, you can do so by editing the Action.
  4. That’s it! Click on any row in the summary table and it should filter related fields and visuals like the Deep Dive Table.
    image

Hope this helps! Let us know if this works or if any other questions.
Thanks!

1 Like

@Giridhar.Prabhu Thanks for your response. I don’t have two datasets though. it’s a single dataset populating both views yet I’m unable to create an action filter between the two

@ kanakatv Thanks for your response. The steps you outlined are exactly what I had already tried before writing this post. This approach works well for dimensions like date, status, and key_ID. However, I’m still running into issues with my calculated metrics.

In the view I provided, clicking on the numbers in the top pivot table filters the site and date, but it doesn’t filter any of the metric rows. This is where I’m running into challenges.

For example, I want a click on the metric #2 (cut compliant trailers) for any given day and site to take me to the list of compliant trailers. The number of compliant trailers is calculated using the formula:

distinct_countIf({ISA},{is_cut_compliant}=‘Y’)

Both the ISA and is_cut_compliant columns are present in the details table, but the action doesn’t filter the ISAs that are compliant on a given day.

Hi @nebadi,
It’s been awhile since last communication took place on this thread, were you able to find a work around for your case or did you still have remaining questions?

If still looking for a solution, it may be easier to assist or see how the action is working if you’re able to create an Arena view of your analysis.

If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.

Thank you!

Hi @Brett, I’m still looking for a solution here. I’ll check Arena view to learn more

Hi @nebadi,
Following up here, let us know if you’re able to upload a copy of your analysis to Arena view so that we can further assist.

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!

Hi @nebadi,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information if needed.

Thank you!