Forum Discussion
Refresh Error - Duplicate Vale & Many to One
Hi All,
This error (see snip below) has started poping up in my reports. This has only started happening in 2026 and I have had the same basic format running since 2024.
I'm pulling some SalesForce reports for about 8 product divisions that contains data on basic sales transactions. The dollar value of each sale is listed in the "Extended" Column.
Other Columns in the reports include:
- Product Dvision
- Sales Region
- Cust ID
- Product ID
- Invoice #
- # of Units
- Invoice Date
- Ship Date
- State
- Zip code.
I've then combined (Appended) these 8 reports in to a Master Report that I have my measures & other Dim Tables referencing:
- Date Table
- Cust ID Table
- Product ID, Table
- Product Division Table
- Sales Region Table
I'm doing this to get around the 2,000 Row limitation in Sales Force (seperate topic)
All of these Dim Tables have unique values and are on the "One side" of the Many-to-One Relationship.
The error is poping up at random in the base reports (see below). In example shown, the sales value of 24.42 was a duplicate in that column, but other columns such as Invoice Date, Cust ID, Invoice # and Zip Code had different values, when comparing the two rows with the 24.42 value. FYI, Curing is one of the 8 sales divisons.
I don't think adding a "removing duplicate" step in power query, is a solution, since it basically will delete a seperate transaction.
Looking for some advise on this.
Thanks,
Sometimes Power BI seems getting crazy on relations because of metadata cache. Simply rename the column in Report view and try again, if it resolves you can correct the column name again.
Renaming the Column did not work. However, I did create a duplicate of the "Extended" Column, then deleted the orginal column, moved the copy and renamed it back to "Extended". This fixed the issue, at least for now. Why I do not know.
I'm still confused on the orginal error as it stated that the my "Extended" column was on the oneside on the Many to one relationship. This column is on the Many side.
9 Replies
FormworkFan
it has to be with how you are building your model.
If you want to use a Sales table as a dimension table in a "one-to-many" relationship you need one field with unique values to be used as the key of the ONE side of the relationship, otherwise you have a many-to-many relationship.
For the OneSide Table: You don´t need to have a table with "distinct registers"but you need one field with distinct values to used as the key of the relationship ensuring the distinct values of your ONE side of your relation ship.
As you have told, it seams to be that your sales table is a Transactional (Not dimensional) Table.
I hope this helps.
If this response was helpful in any way,
I’d gladly accept a kudo.
Please mark it as the correct solution.
It helps other community members find their way faster.Thanks for the Reply.
I don't think I'm trying to use my Sales Table as a Dim Table. Below you can see how I have my model set up.
I have 5 Dim Tables (with unique values - One ) coming back to my Sales Table (Many).
All of these relationships are Many to one with the cross-filter direction set to single.
I'm not sure how I can have a column in my sales table that will always have a unique value, unless I can create a column with a row counter or something like this.
The "Extended" or Sales column in my transactional tables are listed as my sort columns by default. I can only assume this was set alphabetically.
FormworkFan Please confirm which table in this model is the one associated with the Table "2026 PBI Curing" that is reported in the warning error. Please confirm if there is any table in this model with a field called "Extended" in the ONE side of the relationships.
Sometimes Power BI seems getting crazy on relations because of metadata cache. Simply rename the column in Report view and try again, if it resolves you can correct the column name again.
Renaming the Column did not work. However, I did create a duplicate of the "Extended" Column, then deleted the orginal column, moved the copy and renamed it back to "Extended". This fixed the issue, at least for now. Why I do not know.
I'm still confused on the orginal error as it stated that the my "Extended" column was on the oneside on the Many to one relationship. This column is on the Many side.
Hi FormworkFan
I wanted to check if the issue you were experiencing has been resolved. Please feel free to contact us if you have any further questions.
Thank you.
