Forum Discussion

butteredtoast's avatar
butteredtoast
New Member
2 years ago

Ambiguity issue

Hi,

 

I have these three tables:

 

The dates are connected to DateTable[Date]. Everything is fine, however I need to make a relationship between Date[Ledger no] and Ledger[Ledger no]. This would be a many-to-many relationship and the moment I tick the "make this relationship active" box I get the prompt that I can't make this relationship active because it would introduce ambiguity between DateTable and Table.

 

But here comes the fun part. If I do this relationship first (Table[Ledger no] and Ledger[Ledger no]) and then make the relationship between DateTable and Table (using dates), I don't get any prompts about amibugity, both relationships are active. Moreover I realized that if I make the above mentioned inactive relationship, I can make it active after the dialogue box disappears with no problem.

 

Can someone explain to me what happens? I tested my data and filters and everything seems fine, shows what should be shown, but I got a little discouraged after the ambiguity prompt.

 

Thank you in advance.

 

Need Help

2 Replies

  • lbendlin's avatar
    lbendlin
    Super User
    2 years ago

    Unlike a Network Graph database Power BI cannot work with multiple simultaneous paths between any two tables in your data model.

     

    Instead of messing with your data model (which is fine as it is)  use TREATAS to project filters from one fact table on another fact table.

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi butteredtoast ,

    If I understand correctly, the issue is that you want to make a relationship. Please try the following methods and check if they can solve your problem:

    1.Power BI generates an ambiguity warning when there are multiple paths for filter propagation, which can lead to unexpected results in the report.

     

    2.Ensure that every table involved in the relationships has a identifier column to establish connections.

     

    3.Use single directional relationship.

     

    4.Review the data model to identify potential paths.

     

    5.Consider adding a bridging table to avoid many-to-many scenarios.

     

    Best Regards,

    Wisdom Wu