The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi
We are going to change ERP system and I have to alter my data so we can upload it in the right format to our ERP system.
Here’s my current setup:
All relevant columns are formatted as Text via Power Query.
I use a central Name table, which contains unique rows per 4-digit-code.
This code links both to Planning and RM_Film via bidirectional one-to-many relationships (Name is on the "one" side).
There are no blanks or mismatches—codes are clean.
Additionally:
I created a small Fixed table with static values, joined to Name using an Index column.
I use calculated columns like this:
GEWEI =
I’m trying to build a table visual containing selected columns from Name, RM_Film, and Planning, structured to match our ERP import format. It needs to be dynamic so we can run multiple simular reports when we test our ERP.
What’s baffling:
CLASS_01 | DWERK | VERSG | KTGRM | MTPOS | MTVFP | TRAGR | LADGR | PRCTR | STAWN | MTVER | HERKL | HERKR | EKGRP | EKWSL |
FPFILM | BE40 | 1 | YY | NORM | F1 | 1 | 1 | GC-AAV | 48115900 | 1 | BE | B10 | A002 | |
FPPAP | BE40 | 1 | YY | NORM | F1 | 1 | 1 | GC-AAV | 48025515 | 1 | DE | B10 | A002 |
Our database server runs Excel 2010, which lacks modern Power Query features.
I prefer to visualize and manage relationships transparently in Power BI.
It worked yesterday—and now it doesn’t. I’d love insight into what could be causing this inconsistency.
Any help or ideas would be amazing. Thanks!
Solved! Go to Solution.
Hi @Databasic - Only keep Name → Planning and Name → RM_Film relationships as single-directional (one-to-many, from Name to Planning/RM_Film). That’s usually safest.
When both are set to bidirectional, Power BI may struggle to resolve filter propagation, especially when you try to pull data into a single visual that includes columns from all three tables errors like , ambiguous filter paths. Avoid bidirectional joins unless truly needed.
suggest you, make them single-direction from Name → Planning and Name → RM_Film.Use that table for your ERP export visuals/reports — reliable and isolated from model quirks.If needed, use slicers from Name or Fixed tables to make dynamic test versions.
Bidirectional relationships and ambiguity in DAX - SQLBI
Hope this helps.
Proud to be a Super User! | |
Thankyou, @rajendraongole1, for your response.
Hi Databasic,
We appreciate your question on the Microsoft Fabric Community Forum.
Based on my understanding of the issue, please find attached a screenshot and a sample PBIX file that may assist in resolving the matter:
We hope the information provided helps to resolve the issue.
Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.
Hi @Databasic - Only keep Name → Planning and Name → RM_Film relationships as single-directional (one-to-many, from Name to Planning/RM_Film). That’s usually safest.
When both are set to bidirectional, Power BI may struggle to resolve filter propagation, especially when you try to pull data into a single visual that includes columns from all three tables errors like , ambiguous filter paths. Avoid bidirectional joins unless truly needed.
suggest you, make them single-direction from Name → Planning and Name → RM_Film.Use that table for your ERP export visuals/reports — reliable and isolated from model quirks.If needed, use slicers from Name or Fixed tables to make dynamic test versions.
Bidirectional relationships and ambiguity in DAX - SQLBI
Hope this helps.
Proud to be a Super User! | |
This web page gave me the right understanding of relations to troubleshoot. I had to dive into the data and was able to pull out some duplicates to remove the indirect many to many relation. Resolved, thanks a lot 💪