Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello,
I'm french so sorry if it's not clear 😉
I have 2 questions on the same topic. I'm sorry but I am not allowed to send the dataset.
1 - I'm trying to find a better solution to explore 2 basis containing a nomenclature (1st component and 2nd the assemblies)
Here is an example of what I did
I duplicatate my basis 7 time to have my 7 level (which are not used in all cases)
I also add each time a table with only Item_Code to avoid a many to many relation
Assemblies level1 -- Bill_Item_code --> Component level1
Component ---------ItemCodeSite----> ItemCode
ItemCode------------ItemCode--------> Assemblies level2
and so one
It works but it's heavy .
2 - If I select one table at a time I have a good filter behaviour BUT when I try to Union this differents tables it didn't filter anymore
I really hope someone can help me
Take care
Yannick
Hi @Yannick63 ,
This is unnecessary and will increase the size and complexity of the model.
PowerBI supports many-to-many relationships. You can directly establish many-to-many relationships and create measures to complete the calculation logic.
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
110 | |
94 | |
81 | |
66 | |
58 |
User | Count |
---|---|
150 | |
119 | |
104 | |
87 | |
67 |