Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello,
I run a scheduled update for my data from a file that has 8 tabs creating 8 tables from a sharepoint drive. the Source.name file in all is the same vale (the source file) but in one table it is not updating and saying that the data is duplicate. I am at a loss on how to correct this. Here is the error message I keep getting. I believe it has to do witht he way the data model set up when I did the initial import of data.
Data source error: Column 'Source.Name' in Table 'Edgerton' contains a duplicate value 'Data for Roll Out.xlsx' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table. Table: Edgerton.
Cluster URI: WABI-US-CENTRAL-A-PRIMARY-redirect.analysis.windows.net
Activity ID: e0d07a2b-28ad-43e5-bfb7-17cb201fd94f
Request ID: 36b389d4-2b78-b5eb-c783-2c0fed6fc0a0
Time: 2024-05-13 15:39:48Z
Any help is appreciated, Thanks Ron
Solved! Go to Solution.
In your 'Edgerton' table you are using a column as the one side of a one to many relationship. The error is telling you that there are duplicate values in that column, or there are blanks in that column.
One path forward is to identify the column in question and add a remove duplicates step to the query. If blanks are your issue you can filter them out prior to updating the model as well.
Of course the best practice would be to analyize your table to understand why there are duplicate or blank values and correct the problem at the source.
Hope this helps.
Proud to be a Super User! | |
In your 'Edgerton' table you are using a column as the one side of a one to many relationship. The error is telling you that there are duplicate values in that column, or there are blanks in that column.
One path forward is to identify the column in question and add a remove duplicates step to the query. If blanks are your issue you can filter them out prior to updating the model as well.
Of course the best practice would be to analyize your table to understand why there are duplicate or blank values and correct the problem at the source.
Hope this helps.
Proud to be a Super User! | |
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
89 | |
81 | |
65 | |
64 | |
59 |
User | Count |
---|---|
171 | |
115 | |
107 | |
74 | |
69 |