Ambiguous path between tables in Lakehouse not in Desktop

[carg]

I am trying to set up a semantic model in the Lakhouse. I have brought in my tables via sql endpoint but when I try to connect them I keep getting ambiguous path errors. However I have the exact same model set up in power bi (exact same tables from same sql endpoint) with these relationships in place, no issues. Are tables/relationships inturpretted differently in lakhouse than they are in desktop or why might I be experienceing this? first image is lakehouse. second is desktop with the relationships I need to achieve.

here's the lineage

[lbendlin · Accepted solution]

The connection from dim_individual to fact_all_individual_activity is the wrong way round, should be 1:*

[Anonymous · Accepted solution]

Hi @carg ,

Thanks for the reply from lbendlin . I agree with him, and I have something to add to the point he mentioned:

• In Lakehouse from dim_individual to fact_all_individual_housing should create a 1:* relationship, which you created in power bi desktop but not in lakehouse.
• In Lakehouse from dim_date to fact_all_individual_activity should create a 1:* relationship, which you created in power bi desktop but not in lakehouse.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[lbendlin · Accepted solution]

The connection from dim_individual to fact_all_individual_activity is the wrong way round, should be 1:*