This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I am struggling with getting my visuals to interact correctly. The visuals are from the same table. The columns of interest in the table are Child ID, Event, and Event Status. Every ID number is associated with an Event called Pre DECA. Those with an event status of "fail" on the Pre DECA's receive a rescreen, called a Mid DECA. Failed Mid DECA's get a rescreen, called a Post DECA. The Pre DECA, Mid DECA, and Post DECA are all in the same column - the Event column. The pass/fail is in the Event Status column.
What should happen: When the user clicks on "Fail" on any visual, all visuals in that row should respond. Here is an example from last year's PowerBI. Here I have clicked on "Fail" on the EHS Teacher DECA visual and the visual to the right adjusts.
What does happen: When the user clicks on "Fail" on any visual, the other visuals fade, but do not interact.
The slicers at the top of the page work just fine - all visuals interact when a slicer is selected. For example, here I have selected "Male" under the "Gender" slicer, and you can see that the numbers have all changed. The slicers are from a different table, with the relationship many to many.
I have read numerous posts about visuals not interacting, but the most common solutions seem to be checking that the relationships are correct (all relationships with this table are many-many) and that the visualizations are turned on (the filter visualizations icon is active on all visuals on the page). Not sure what else to try. Can anyone help?
Hi @Melodyv ,
According to your statement, I think your issue should be casued by your data model.
Firstly, please make sure whether [Gender] column and the [DECA Fail/Pass] columns are in the same table. I think they may not in the same table, and many to many relationship will cause this issue. You can try to add Dim table to create Star structure
For reference: Understand star schema and the importance for Power BI
Apply many-to-many relationships in Power BI Desktop
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 27 | |
| 25 | |
| 25 | |
| 21 | |
| 14 |
| User | Count |
|---|---|
| 50 | |
| 46 | |
| 23 | |
| 18 | |
| 18 |