Bug in Relationship dialog - incompatible data types

[edhans]

Regardless of the data types, the Create New Relationship dialog box reports the columns are of a different type. It will let me click OK and create the relationship, but it is still wrong info. You can see both of these are DateTime datatypes. I've repro'd this with strings too.

This remains an "error" if you save it, then open it back up to edit it.

There is no error in the Relationship view of the TOM panel.

[mlonsk]

Hi @edhans
I have reproduced this bug and we will look into fixing it.
Thank you for reporting.

[redstor-albe]

Seeing the same issue where showing incompatible data types. However, my visualizations in Power BI that uses that relationship doesn't seem to work either, nor measures using those relationships. Is it just a display issue in the software and my problem might be somewhere else or is this also seen somewhere else? I'm on 3.5.0.1077

[mlonsk]

Hi @redstor-albe
The issue that is being reported here is according to our testing only a display issue, ie. TE is showing incompatible datatypes though they are the same. It should not affect the actual relationship being created.

Are you able to provide is with an example of what the relationship is you are setting up, properties etc and the error you are seeing in Power BI?
Does the same issue occur if you create or modify a different relationship?

[redstor-albe]

Hi @mlonsk

After posting this message yesterday I have since downgraded to 3.4.2 - my problem still persisted so I deleted the relationships and recreated them, that seems to have solved the problem. One case I had was one to many between my date table and a fact table containing some data and dates, the other was a 1:1 relationship using GUIDS. All stopped working but after recreating them and refreshing the model everything worked.
Don't think it was related to this bug.
By the way it was definitely in the model (AAS hosted) - I could see the relationships not working in PBI, Dax Studio and Tabular Editor.

[otykier]

This is fixed in 3.5.1.