My team would like to dynamically show certain visuals when a row in a particular table/visual is selected. We have found that there is no ability to update parameters via a Select Action, which is the only input to a rule for conditional rendering. We think this could be possible if we could update a parameter from a Select Action, or if there was an input to conditional rendering rules based on a selected row.
Unless I am missing something. You can update a parameter from a select action.
This is an action that gets activated when I click on a row in a table. It selects the customer_name field from the selected row in the table and set the CusotomerName parameter. In this case I am staying on the current sheet because I want to manipulate the other visuals.
We have tried something similar. This didn’t work for us since the behavior is slightly different than just updating a parameter without a navigation action.
The navigation action causes the selected row to not appear as selected, and that means there is not a good interface for unselecting that row as well as potentially confusing the user.
Hi, @Patrick. Did @Andy_Brand’s solution work for you? I am marking his reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community Q&A Forum!
Thank you for this! I’ve been pulling my hair out, trying to use ON SELECT Filter action to update a parameter. It’s completely counterintuitive to have to use a Navigation Action.
I have two visuals right now, the top one is just a table of clients (and some other info) and the bottom one has much more detailed information relative to whatever client is selected in the top visual. I wanted both the Title of the bottom visual and the filter to be updated at the same time when the client was selected in the top visual. Your answer here solved both problems.
For the filter, there is a custom filter option that I just set to “equals” and then the parameter being set in the top visual’s ON SELECT Navigation Action, with the source being the client Field in the dataset. Works great now!