Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I'm working with a data source, which is a list of audit findings stored in SharePoint. The findings are assigned to an audit ID, to connect them to the audit in which they were raised. A row in the data source contains both the (unique) finding ID and the audit ID. Users asked for a dashboard in which they could view details of the findings per audit.
So I made two tables, both in Fields and Visualizations:
My intention was to let the user select the audit in the first table, and then select a finding from the second table (which at that point contains all the findings raised in the selected audit):
As you can see, the first part works. As does the second part, however, when selecting a finding in the second table, the filter gets removed from it, even though the data is being filtered on the selected finding and the audit ID doesn't change:
This is not user-friendly, as the user can't see the selected item anymore without scrolling through thousands of other findings. It also then requires the user to click the audit field again to bring back the (on audit) filtered list. I understand that a slicer can be used, but I like the uniformity of this solution. What causes behavior? How can this be done (differently) in a nice way?
Solved! Go to Solution.
When you click on the second table, the selection on the first table is cleared. That's just how selection works for tables (selections don't persist on further clicks). If you want to preserve the selection while clicking on the second table, you'll need to use a slicer.
What's happening when you click on the second table, is that this table is now filtering the first table instead of the other way around. If you want, you can turn this interaction off by selecting the second table and using Edit interactions under the Format tab and turning off interactions in that direction.
When you click on the second table, the selection on the first table is cleared. That's just how selection works for tables (selections don't persist on further clicks). If you want to preserve the selection while clicking on the second table, you'll need to use a slicer.
What's happening when you click on the second table, is that this table is now filtering the first table instead of the other way around. If you want, you can turn this interaction off by selecting the second table and using Edit interactions under the Format tab and turning off interactions in that direction.
Alright, I suspected it was something like that; I just liked the setup with two uniform tables instead of a slicer and table, but I need to take a different approach then.
User | Count |
---|---|
98 | |
75 | |
74 | |
49 | |
26 |