USERELATIONSHIP Issue

Hi Oliver_Buchanan​
Thanks for all the testing you've done — that detail really helps.

The key clue is that your measure returns the MAX of the whole ActionEvent table. That means no filter is reaching ActionEvent at all.

Here's why. USERELATIONSHIP switches a relationship on, but it doesn't change which way the filter flows. Your relationship goes one-to-many from ActionEvent to Action, so filters naturally flow from ActionEvent down to Action. Your measure needs the opposite — it filters on Action and reads from ActionEvent. That direction simply isn't open, so nothing gets filtered.

The CROSSFILTER measure suggested earlier didn't test this properly, because it was missing USERELATIONSHIP. Without that, the relationship stayed switched off. You need both together:

************************************************
CollectionActionEventTimeuse = CALCULATE ( MAX ( 'ActionEvent'[Created] ), USERELATIONSHIP ( 'Action'[CollectionActionEventKey], 'ActionEvent'[ActionEventKey] ), CROSSFILTER ( 'Action'[CollectionActionEventKey], 'ActionEvent'[ActionEventKey], BOTH ) )
************************************************

If that still doesn't work, run this in DAX Studio to see what your model has actually saved for each relationship:
************************************************
EVALUATE INFO.RELATIONSHIPS ()
************************************************

Look at ToCardinality, CrossFilteringBehavior and IsActive for the one you're activating. Web-based semantic models don't validate these settings when you create them, so they aren't always what you'd expect.

Either way, your TREATAS measure is perfectly fine to keep — it filters the column directly, so it avoids this problem entirely.

References:
USERELATIONSHIP function

CROSSFILTER function

Model relationships in Power BI Desktop

Thanks,
C Srikanth
Community Support Team