Not recognizing date relationship

[mkohler281]

I am trying to create a column to compare two dates but the error is saying there's no relationship. This is a many-to-one relationship from a schedule to a list of records. Both dates are formatted correctly. Any ideas why this relationship is not working? Not sure what the curly brackets at each end of the relationship is representing.

[mkohler281 · Accepted solution]

Thank you for the help, I ended up changing the storage to Import which fixed the relationship so it was no longer limited.   

[Anonymous]

Hi @mkohler281 ,

As @vojtechsima said, In Power BI Desktop model view, you can interpret a relationship as being limited. A limited relationship is represented with parenthesis-like marks ( ) after the cardinality indicators.

A model relationship is limited when there's no guaranteed "one" side. A limited relationship can happen for two reasons:

• The relationship uses a many-to-many cardinality type (even if one or both columns contain unique values).
• The relationship is cross source group (which can only ever be the case for composite models).

There are some restrictions related to limited relationships:

• The RELATED DAX function can't be used to retrieve the "one" side column values.
• Enforcing RLS has topology restrictions.

For @vojtechsima's workaround, because his storage mode is Import, the MAXX() function could work , but your storage mode is DirectQuery, there are many limitations for this storage mode

MAXX function (DAX) - DAX | Microsoft Learn

You need to re-create your data model or try to create model in SSAS.

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[vojtechsima]

Hello, @mkohler281 ,

the brackets represents a "Limited relationship" and RELATED is not supported in those:

https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand

You can have a workaround or resolve the "limited relationship".

The Workaround can look like this:

Column = 
var currentRow = 'fact'[Test]

var matchingRows = MAXX(FILTER(dim, dim[dim] = currentRow), dim[dim])

return matchingRows

you don't even need a relationship for that:

[mkohler281]

Thank you, but it looks as though this does not work in Direct Query.