Cross Filter with visuals

Hi Kay_Kalu​,

I think the issue is more with the data model than the DAX itself.

The visuals on the left are based on TaskOccurrences, while the visuals on the right are based on Team Workload. The filter is flowing from TaskOccurrences to Team Workload, which is why selecting a bar on the left updates the visuals on the right. However, the reverse doesn't work because there isn't a valid filter path back to TaskOccurrences.

I noticed you tried changing the MJ_Number relationship to Both directions, but Power BI throws an ambiguous path error. That usually happens when there are multiple routes available for filters to travel between the same tables, so Power BI doesn't know which path to use.

Rather than enabling bi-directional filtering, I'd recommend creating a dedicated MJ_Number dimension table containing unique MJ numbers and connecting both TaskOccurrences and Team Workload to that table. Then use the dimension table in slicers and visuals that need to interact across both fact tables. That's generally the cleanest approach and avoids ambiguity issues.

If changing the model isn't an option, you could also use TREATAS() in the measures for the Team Workload visuals so that selections from TaskOccurrences are applied virtually without changing relationships.

Something like this:

BAU Count =

CALCULATE(

COUNTROWS('Team Workload'),

TREATAS(

VALUES(TaskOccurrences[MJ_Number]),

'Team Workload'[MJ_Number]))

Based on the model screenshot, I'd personally go with the shared MJ_Number dimension table. It will make cross-filtering much more predictable and save you from relationship issues later on.