Relationship object named '9f27fe72-cedb-877b-063e-d2f60d86d75e'

[gpapashvili]

Hi,

I've got following error "This expression refers to a Relationship object named '9f27fe72-cedb-877b-063e-d2f60d86d75e', which has an error". This is not first time I've got this kind error, and every time I have to go and look for several hours to find out what exactly is causing error.

Is there any easyer way to find to what relationship '9f27fe72-cedb-877b-063e-d2f60d86d75e' this identifier refers? to find and fix errors easyer?

I am currently in testing phase of Power Bi services and until my trial will be finished and will purchase couple licensis I want to know if it worth to buy product. I'm getting data from various sources and they are messy, and there is no chance to correct data in the sourse and if every time I have to spent my time on things like this (searching unrecognized error names), I'd rather will change product.

[v-nmadadi-msft]

Hi @gpapashvili 
I wanted to check if you had the opportunity to review the information provided by @cengizhanarslan , @maruthisp  and @TomMartens . Please feel free to contact us if you have any further questions.

Thank you.

[cengizhanarslan]

Unfortunately, Power BI doesn’t expose a friendly mapping from that GUID to “which relationship” in the UI. That GUID is an internal object ID, so the error message is not very user-friendly. That said, there is a couple of practical ways to identify the exact relationship quickly.

If you can use Tabular Editor (external tool), you can find the relationship by ID.

1. Open your model in Power BI Desktop

2. External Tools → Tabular Editor(You need it install this firts)

3. Go to Model → Relationships

4. Use search / inspect relationships and look for the one with an internal name/id matching the GUID (depending on TE version, it can show the internal object id in properties)

[maruthisp · Accepted solution]

Hi @gpapashvili ,

As per my understanding, can you enable dax query view or use DAX studio and try below DAX query:

EVALUATE
FILTER(
INFO.VIEW.RELATIONSHIPS(),
[Name] = "9f27fe72-cedb-877b-063e-d2f60d86d75e"
)

The most common fixes for the above problem after finding the relationship:
1. Data Type Mismatch between the two join columns

2. Non-unique values on 1 side of 1-many relationship

3. Blank/invalid keys

If this reply helped solve your problem, please consider clicking "Accept as Solution" so others can benefit too. And if you found it useful, a quick "Kudos" is always appreciated, thanks! 

Best Regards, 

Maruthi 

LinkedIn - http://www.linkedin.com/in/maruthi-siva-prasad/ 

X            -  Maruthi Siva Prasad - (@MaruthiSP) / X

[gpapashvili]

Thank you. Didn't know DAX can do this. 👍👍👍

[TomMartens]

Hey @gpapashvili ,

I have never faced this error. Could you please provide details on how you resolved this error in the past?

Maybe it's pointing to a lineage tag you can search for in the TMDL view in Power BI Desktop.

Regards,
Tom

[gpapashvili]

Before just using trial and error, but now @maruthisp provided great solution.