Model cycles

[Anonymous]

Hi,

I'm curious how can one handle cyclic dependencies. Let's say we have four tables: Users, Desktops, Orgunits and Tasks. Each Orgunit has some Desktops assigned and some Users working on those devices. Each Task is being executed by a User on a Desktop BUT there is an option that User can from time to time work for another Orgunit on their Desktops. Now we have to maintain all the informations:

• what Desktops belong to what Orgunits (*:1)
• what Users are formally assigned to which Orgunit (*:1)
• which Users performed certain Task (there may be more than one) (*:1)
• what Desktop was used while performing the Task (1:1)

So far my model has duplicated Desktop table so there is no cycle but I'd like to avid having the very same table added twice.

This is of course very simplified model of my real situation (I've got some more tables between Users and Tasks and the whole model is not finished yet, might happen that cyclic dependency will pop up again later).

What are your advices? What are the best practices?

[Anonymous]

Hi @Anonymous ,

I'm not sure if my understanding is correct or not...Do you want to know how to avoid the circular dependency when create the data model(similar with the one in below screen shot)?

Please check if the following documentations can help you:

Adjusting Cross filter direction for a complex set of tables and relationships

What is the Direction of Relationship in Power BI?

Best Regards

Rena

[Greg_Deckler]

Sorry, not following this. Please see this post regarding How to Get Your Question Answered Quickly: https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490

[Anonymous]

@Greg_Deckler, with all respect could you be more specific on what's wrong with my post? I'll try to improve it but I really honestly don't know which point do you find missing/missleading. What point(s) from linked post do you refer to?

[Greg_Deckler]

I think the post is pretty clear if you read it and compare it to what you have posted:
1. Sample data
2. Expected output
3. The logic of how to get from A to B

You included you data model relationships.