Ambiguous Relationship - Best Practices

[Powerbi1979]

Hi,

From a data modelling perspective, what is the perferred best practices solution to the following situation? In this case, the Organization dimension exists on both Employees and Projects, and the FactLabor table joins to both Employees and Projects - hence the circular relationship.

A second dimension table for organization (one for project one for employee) and sync slicers? I just want to know from a modelling stand point the best practices in this case. Perhaps there is a way to explicitly define join contexts or something like that.

 

 

[amitchandak · Accepted solution]

@Powerbi1979 , As there are two paths to fact you can not join.

Two option

1. keep it independent and filter measure and slicer using the selected values

Slicer  filter example

How to filter the slicer of a disconnected table: https://youtu.be/cV5WfaQt6C8

You also need make sure all measures get filtered 

2. Merge it with both dimensions in the power query. but that will not give common filter