Forum Discussion
Helper IOne table to rule them all
Why not merge all of these onto a single Query? Or make 2? Seems kind of overkill to need that many relationships when there aren't many unique columns
MarfieldThis is only an example to explain my problem/need.
My real data model contains about 20 dim tables and 3 fact table soooo... I doubt this would be efficient if I merged everything in only one table 😋
- amitchandak
Super User
Just try to make it active from the property and check what error it gives. I faced the same issue when I tried joining one table by (say ) source not by source Id. I deleted all such join and created all join on source IDs.
Also make sure there are no two paths, which not visible here in diagram.
Why would that not be efficient? That is essentially what relationships are accomplishing. It would solve this issue 100%
- VasTg
Memorable Member
Anonymous
Based on the model screenshot, you cannot make the relationship from source to client as active because of circular reference. Ideally, there should be only one active path, so that power bi will know which path to travese from Source to sales via Product. If all of them is active, it doesn't know it should traverse vis product or client. Thats the reason behind allowing only one relationship as active and rest as inactive(see USERELATIONSHIP in DAX).
If this helps, mark it as a solution
Kudos are nice too
