Is there any workaround to replicate “Buttons” feature from Power BI?
For instance, if there is button option to switch between “Region” & “Country”, the visual should display “Sales by Region” & “Sales by Country” respectively.
In Quick, I am able to do it using parameters which can be shown as radio buttons like a list. But is there any way to show it like the below image attached.
There is a workaround to create a ‘Button’ in Quick Sight. Depending on your use case there are two ways to achieve this. You can utilize the filter or navigation action, or you can create a button that toggles the visuals that are shown.
Here is a previous post that talks about the toggle ability to hide and show certain visuals. From what it sounds like for your case I think this is more of what you are looking for. You basically just overlay the two visuals on top of each other and create a button determines what visual is shown and what is hidden. Toggle button to show / hide visualization - Q&A - Amazon Quick Community
I hope this helps and let me know if you have any questions!
Yes so one workaround I have found to do this is to create two calculated fields and then apply them to a table visuals. What I mean by this is you are going to create a calculated field and in it, you simply put ‘Region’ and then title the calculated field as something like Region Button. Then repeat the same for Country. After that, you apply the button field to a table visual. This may look a little weird as we are essentially creating the button from a specific cell in a table visual. You can turn off titles and column headers and any other design components, but the goal is to just have the cell showing. From there, you then create an action which will be what powers the changes that switches between region and country. I will attach an example below of a button I created.
This is from a Tariff Dashboard I created but you can see that I used what I talked about and created a ‘Reset’ button that is used to reset my parameters. Your use case is a bit different but still should follow the same steps on how to create a button.
Hope this helps and let me know if you need me to explain anything further!
Thanks for the workaround. But I am not able to achieve the expectation.
I did the same by creating two calculations and used in table visual to make it look like button. However, actions cannot be applied there.
I think we can only use rule based hiding for this and we need parameters for that.
If I create parameter, then I need to give control values which will be visible in dashboard. My question is about this only. I don’t want any dropdown/radio buttons/list . I need buttons and when I click the buttons, the respective visuals should show.
Yes this is completely possible in Quick. You are right that even with rule-based hiding that you will still need a parameter. Now where the buttons come in, you will add an action that essentially controls what value the parameter holds, then you will set rule base hiding on your visuals and have them either show or hide dependent on what value your parameter is holding.
So when you create your parameter, have the static value be something simple like ‘select one’. Then for your actions you create a navigation action on your button that essentially picks the value of the parameter. Then for your visuals, you can decide whether to hide or show the visual dependent on if you want the logic to be equal or not equal to the value or the parameter. Moreover, an example can be if you have one visual set as ‘Show if param Does not equal select one’, then the other visual you will set something like ‘Hide if param Does not equal select one’.
Does that help answer your question? Let me know if I need to explain anything further
However, I am unable to follow after creating parameter. It would be helpful if you can explain the step by step approach or with the analysis link that I have attached.
Hi @Kripa,
I went ahead and applied the logic to your Arena view, which you can check out here: Button Test
Jacob was correct when mentioning the use of a parameter in this case, the neat thing about parameters as opposed to filters is you do not need a control present in the dashboard to use or refer to those parameters and their values.
So to sum up in a quick few steps:
Create a parameter that will be used to handle your values for the buttons. So for this, I called the parameter ‘CountryRegion’. I set the default value as ‘Region’. And do not create a control for this parameter
- Then you setup an action ‘Make sure to use Navigation’ for your two buttons. So the action on ‘Country’ button will be, when clicking, you will assign the value ‘Country’ to parameter ‘CountryRegion’. And then for ‘Region’ button, you assign the custom value of ‘Region’ to that parameter.
- So when you click the ‘Country’ button, it will parameter value will change to Country, and when you hit ‘Region’ button, it will change the same parameter to Region.
- Last, create a rule for each of your visuals. That rule will vary based on each visual but will basically say if above parameter equals ‘Country’ show those visuals and vice versa.