I have two table visuals, let say Table 1 and Table 2. Both are now visually shown on initial load of Dashboard. However I want the Table 2 to be shown only when a row in the Table 1 is clicked by the user. There is a Filter Action already configured which loads details in Table 2 based on the row clicked in Table 1. But there is no point in showing Table 2 initially when the dashboard is loaded unless a row is clicked in Table1.
Note: The Filter Action is configured in such a way that The Table 2 details are loaded based on 3 fields available in Table 1. So even if there is any solution available based on Navigation Action it might not work here.
Is there any way we can solve this problem by adding a link / applying conditional rules or any other mechanism?
Hello @Philip - Interesting use case. Can you please try to change the layout to Free form Layout. That will allow you to render / hide visuals based on rule. See the below snapshot for reference. See if this helps!
Did my suggestion help you in resolving your query? If yes, would request you to mark the post as âSolutionâ. This will help the community to find guidance and answers to similar question. Thank you!
I am indeed using the Free Form Layout. How can I use the conditional rule mechanism here? Any help would be much appreciated.
As I said in the previous post, a combination of three fields in Table 1 determine the data to be shown in Table 2. I have done parameter based Hiding/Rendering of visual based on rules in other areas. But in those scenarios there was a static value parameter which can be checked against. Is there any way to set a parameter value when a row is clicked? If possible, then I could have checked that value in rules and show the visual only when that value is set
You can set a parameter value using an action. When creating the action, set the action type to âNavigation actionâ and select your current sheet as your target sheet. Then add your parameter to the action and set its value.
Hello @Philip - I have tried to explain the process in detail based on my understanding of your use case. Please see the below snapshot. Hope this helps!
Did my suggestion help you in resolving your query? If yes, would request you to mark the post as âSolutionâ. This will help the community to find guidance and answers to similar question. Thank you!
Sorry for my late reply. Thanks for the detailed explanation. I understood the explanation. Creating a calculated field, linking a parameter to that field in the Navigation Action of the first Visual so that the parameter gets the value, Show/Hide, based on the calculated field logic. This is then used in Conditional Rules to show/hide the second visual.
Now 2 problems are here. First of all I donât have any specific conditions to check in the calculated field creation. The second table visual have distinct values for each row in the first visual. For every combination of the 3 fields in first visual there are distinct values in second visual. Every row in the first visual is important. So I donât have anything to filter out.
Secondly, If we created a navigation action in the first visual then how will we pass the 3 fields of the first visual to the second visual which determines the rows to be shown? We canât configure multiple actions in the first visual.
Hello @Philip - Thank you for your response. Can you please help me with further understanding of the problem.
As you mentioned that your second visual (child) has distinct values/rows for each row of the first table (master table). In that case, what is the necessity of show/hiding the table as at a given point of time your child visual will always be visible? Is that the right understanding? if that is the case then, you can utilize the filter action alone to just filter the child visual according to your row selection. In that case you can create a calculated filed by concatenating all the necessary fields from the visual to pass into the child visual as filter parameter. Does that make sense or I misunderstood your problem? If you have some sample of your tables, that would be helpful. Thank you!
Sorry, I wonât be able to share the snapshot due to confidentiality. But Iâll try to explain the problem with an example. Letâ say there are two table visuals: visual 1 and visual2. Now Table 1 has fields like Job number, Job Date etc. For each combination of Job number, Job date in first visual, the second visual lists the employees who worked on that particular job and date. Both the visual includes other supporting fields and I have skipped those for ease of understanding. Now when the dashboard is initially loaded by the user in browser, as soon as he sees the second visual it creates a confusion because it lists all the employee names and their metrices for all the dates available in data source. Actually the user should click on any row in visual 1, and thereby view visual 2 entries based on job number and job date he clicked.
Now the filtering of visual2 based on Visual1 is already done via action filter. All I need is to somehow hide visual2 on initial loading by user so that the user doesnât see all the employee entries initially. We could have added fields like Job Number, Job date etc in Visual 2 also so that there will be no confusion. But we donât have enough space in the dashboard. As I said there are other fields also which I have skipped for ease of explanation.
Hence the question, âIs there any way to hide visual2 by default on loading of dashboard and show only when a row data in visual 1 is clicked. If none of the rows are clicked then hide visual 2â.
Hope I have explained it clear. Thanks again for your time.
Thank you @Philip for your detailed response. I get a clear picture now. The expectation that you have seems to be having both Filter Action and Navigation Action on the âSELECTâ only, which according to my awareness and knowledge natively not yet available in Quicksight. The parameter as of now can only be set in navigation action to control the show/hide based on selection. But since Filter action is already configured in Rows, it will not allow to configure navigation action simultaneously. I will dwell on this, but unfortunately right now I donât have any ready-made answer to your problem. Thank you for sharing such problems. It enriches us.
Hi Philip
There is a work around I can suggest which could work, it sounds like your action filter is using a unique key on the job number if soâŚ
Create a calculated field (lets call it âshowtabletwoâ for example) on the dataset used for Table 2.
distinct_count(jobnumber, )
Now create a filter on the second visual using âshowtabletwoâ where the sum is less than or equal to 1. By default (unless you only have one job number) nothing will now be shown.
Your action filter on table 1 will satisfy the filter condition on table 2 when selected and show that job number details. The only downside here is that table 2 will showing No Data found.
Iâve not spend must time on this however it should also be possible to hide the visual based on the calculated field showtabletwo with some additional logic.
Hi @Philip
Did Johnâs or Sagmukheâs Maxâs solutions work for you? I am marking Sagmukheâs reply as, âSolution,â but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community Q&A Forum!
