Shubham Choudhary on 29 Jun 2021 07:54:21
Use case:
To facilitate page navigation , bookmark navigation or even drilldown navigation by doing single click on Particular column in table visual.
Benefits :
By adding such feature , we can design a relevant panel which will be combination of some visuals so based on selection in table visual it will pop out (bookmark navigation will happen).
Even for drilldown navigation also we need to right click and required selection of drill down view .By adding such feature in Table visual , it may avoid one extra click to showcase use full insight to end users.
- Comments (3)
RE: Add "Action" Property for Table or matrix visuals
I also need a similar functionality where one column can contain buttons to navigate to different pages on my report and the page name can be configured as a dax measure, which uses related() function to get a single page name for each row's button based on value of some other column in the table.
RE: Add "Action" Property for Table or matrix visuals
I have a similar need, when the %GT on a table reaches a certain %, I would like to show a warning pop-up. I can create a bookmark for the pop-up, but do not see a way to tie the pop-up to a condition in a table.
RE: Add "Action" Property for Table or matrix visuals
This would be great for my users. It's not obvious when drill-through is available. Not every drill-through page that is listed is relevant in all cases. If I could set a drill through action on a column, I could use field formatting in the table to indicate it is clickable. This would make it instantly discoverable. In this case, the actual drill-through field would be a separate compound key. So, I would want to have any available drill page selectable, not just the ones depending on the field the action is being added to. I have an audit report, with one test per page. I have a summary screen, showing volumes on each test. I've made this link to the related page using the Web URL action, by copying the URLs from the published dashboard and storing it in a lookup table. This isn't ideal as it requires a publishing cycle to get the URL, plus the link opens in a new tab rather than keeping in the same one.If there was a dynamic page navigation action, I could make the lookup instead store the page name that relates to the test. This would be more obvious when reading the lookup table what the link will do, and if it is correct. It will preserve proper navigation in the dashboard. The links will still work even if the dashboard location changes.