Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Anonymous
Not applicable

Slicer does not interact right - Relationship problem

Hi Power BI Community!

I have this: Complaint rate = Q2 Count / WE Buchungen * 100. That is correct. Know I have slicer with the suppliers

Beginner_2020_0-1619419420045.png

The Q2 nummer count by the selected supplier is right but the WE Buchungen does not change! = Complaint rate is wrong

Beginner_2020_1-1619419608285.png

 

The Q2 Count comes from the table Stammdaten (3) and the WE Buchungen comes from the table Bestellung_WE.

They are connected by ID. 

Beginner_2020_2-1619419729466.png

 

Want is wrong? Both tables are connected with a date table. Is there something wrong?

 

2 ACCEPTED SOLUTIONS
Anonymous
Not applicable

@amitchandak Thanks for the video! 
I created a supplier ID of each of the tables. I also notice when i select both suppliers as a slicer it works but this is not ideal. 

Lieferant = DISTINCT(UNION(ALL('Stammdaten (3)'[LieferantID]), ALL('Bestellung_WE'[LieferantenID])))

Beginner_2020_0-1619428575764.png

 

but still it does not react at all...

View solution in original post

V-lianl-msft
Community Support
Community Support

Hi @Anonymous ,

 

Is we buchungen a column or a measure?

I can't clearly understand the problem with the picture you provided. You can try to create we buchungen related measure and then limit the filtering conditions in the formula.

Sample data and expected output will be helpful to provide an accurate solution.

https://community.powerbi.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-Forum/ba-p/963216 

 

Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

View solution in original post

5 REPLIES 5
V-lianl-msft
Community Support
Community Support

Hi @Anonymous ,

 

Is we buchungen a column or a measure?

I can't clearly understand the problem with the picture you provided. You can try to create we buchungen related measure and then limit the filtering conditions in the formula.

Sample data and expected output will be helpful to provide an accurate solution.

https://community.powerbi.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-Forum/ba-p/963216 

 

Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

amitchandak
Super User
Super User

@Anonymous , Not very clear. from where the supplier filter is coming - is it coming from a common dimension?

 

if not it should come from the common supplier table

https://www.sqlbi.com/articles/the-importance-of-star-schemas-in-power-bi/

Anonymous
Not applicable

@amitchandak I have the suppliers in both tables and take one of them in the slicer visual. What is the right way to do it?

@Anonymous , Ideally two fact should not join, I am assuming these two are not joined.

So you can create a common table for supplier and use it

 

refer Bridge Table: https://www.youtube.com/watch?v=Bkf35Roman8&list=PLPaNVDMhUXGaaqV92SBD5X2hk3TMNlHhb&index=19

Anonymous
Not applicable

@amitchandak Thanks for the video! 
I created a supplier ID of each of the tables. I also notice when i select both suppliers as a slicer it works but this is not ideal. 

Lieferant = DISTINCT(UNION(ALL('Stammdaten (3)'[LieferantID]), ALL('Bestellung_WE'[LieferantenID])))

Beginner_2020_0-1619428575764.png

 

but still it does not react at all...

Helpful resources

Announcements
Sept PBI Carousel

Power BI Monthly Update - September 2024

Check out the September 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Sept NL Carousel

Fabric Community Update - September 2024

Find out what's new and trending in the Fabric Community.