Forum Discussion
PowerBI Slicer Not filtering Visualizations properly
- Anonymous1 year ago
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,
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
- abarrow1 year agoNew Member
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.