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 have a current PowerBI visualization that I have set up by entity. I go to slice by a specific entity, and half of the visualization does not filter correctly (i.e. the numbers do not match what is in the excel file). The part that does not filter correctly is the "IA Exceptions" table and I am filtering by "Employee Org Name" on the "Employee Mapping" table. Originally, the data was all combined, but I thought splitting it out would fix the issue (it did not). Is there a reason why this would happen?
Solved! Go to Solution.
Hi @abarrow,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Your slicer on [Employee Org Name] (from Employee Mapping) isn't filtering the IA Exceptions table correctly because there's likely a mismatch between the relationship fields. Employee Mapping uses an [Employee] ID, but IA Exceptions uses [Employee Name], which may not match exactly. As a result, the relationship doesn't propagate the filter properly.
Best Suggestion:
Update your data model so that IA Exceptions includes the same [Employee] ID used in Employee Mapping, or create a proper relationship using matching keys (e.g., Employee ID, not names). This will allow the slicer to filter all visuals consistently.
If this information was helpful, kindly mark the response as accepted and give it a thumbs-up so it can assist others as well.
Best regards,
Prasanna Kumar
Hi @abarrow,
Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.
If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful this will benefit others in the community as well.
Best regards,
Prasanna Kumar
Hi @abarrow,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Your slicer on [Employee Org Name] (from Employee Mapping) isn't filtering the IA Exceptions table correctly because there's likely a mismatch between the relationship fields. Employee Mapping uses an [Employee] ID, but IA Exceptions uses [Employee Name], which may not match exactly. As a result, the relationship doesn't propagate the filter properly.
Best Suggestion:
Update your data model so that IA Exceptions includes the same [Employee] ID used in Employee Mapping, or create a proper relationship using matching keys (e.g., Employee ID, not names). This will allow the slicer to filter all visuals consistently.
If this information was helpful, kindly mark the response as accepted and give it a thumbs-up so it can assist others as well.
Best regards,
Prasanna Kumar
I added Employee ID to the equation and made that my unique ID. I thought name would be unique enough but turns out the ID is definitely much better for slicing.
It looks like you have the relationship and filter direction set properly between the two tables. Can you give us more detail, like maybe a screenshot of a report, or better, some sample data? What fields are in play in the relationship? [Employee Name] and [Employee Org Name] ?
Proud to be a Super User! | |