Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
This will be the 2nd time I'm having this problem. Something changes and my model breaks. I don't know what happened. I made no delibrated change. I start to receive this message. Last time to fix it I deleted the query and rebuilt it. Is there something I'm missing or doing wrong? Is there a way to revert a file back in history?
You can create the many-to-one relationship successfully at first. But if the Invoice Id column in “Sold By Sales Detail Report” changes later as following screenshot, you’ll receive the warning message once you refresh the tables in Power BI Desktop.
For creating and managing relationships in Power BI Desktop, please refer to this document. In a many-to-one relationship, at least one column in one of the tables must contain unique values.
Best Regards,
Herbert
@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 @Seth_C_Bauer 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?
@Seth_C_Bauer 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.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
144 | |
76 | |
63 | |
51 | |
48 |
User | Count |
---|---|
204 | |
86 | |
64 | |
59 | |
56 |