Forum Discussion
Query Breaks and I don't know why
GEN3Electric Couple things I'll mention:
1) For future snapshots, I find that "Snipping Tool" in Windows works really well to capture images (rather than taking photo's)
2) You may want to delete the second photo as it contains personal information (unless that is all test data)
3) It looks like your underlying data set contains duplicate rows, so however that process is updating data needs to be modified so that it doesn't pull duplicates in to Power BI -> This is why you are getting the error.
One side of the relationship in Power BI always has to stay unique.
Thank you Anonymous but:
1. Snipping Tool is great but it would not work with an open Dialog box.
2. I did delete the 2nd Photo. It was a publicly avalable data set of property records.
3. I have udated & refreashed the inderlying data set dozens of time with no problems. I have looked for duplicates in excel and seen none. The reports the info comes from should not have any dulplicats in it. Something is changing in the file. last time this occurerr I deleted the bad query and requried the same info and it was fine.
GEN3Electric hmm. I have mine on my toolbar and I can use it any time. You could also screen shot by alt + PrtScn, then snippet that. - all of which doesn't help you at all with your initial question. Sorry.
"Deleted the bad Query" - what is this query step doing?
Anonymous I just added it to my tool bar. Thank you for the tip.
I deleted the connections in the data model one by one and found the problem connection. There is still something odd about it. I think that some how the model is changing. Could there be some auto detecting of a realatinship occuring? I'm sure it is something incredibly stupid obvious that I just can't see.
GEN3Electric The error is really specific to value and table... Which is why my initial assumption is that if you can create the relationship on the column, and then it goes bad in the future, that the underlying data set is changing to include the duplication when you open/refresh the Power BI model. If it existed, it wouldn't let you build it.
Just tested the above:
I can replicate the exact same error by creating the model, building the relationship, then updating the data source. When I refresh the model in Power BI, I get the same error calling out the explicit column names and value.