Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
CyrilleC
New Member

Scheduled Refresh failed

Hello,

I have the following message after the scheduled refresh :

Erreur de source de données: Column '<oii>N° Inventaire</oii>' in Table '<oii>Equipement</oii>' contains a duplicate value '5929936137' 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: Equipement.
URI du cluster: WABI-NORTH-EUROPE-K-PRIMARY-redirect.analysis.windows.net
ID d'activité: 4cccdb88-6d2a-4843-a113-74b29b0b0296
ID de demande: c755123d-674c-a81b-f659-53e67a6ed47b
Heure: 2024-07-10 07:57:16Z

My problem is that this message does not appear everytime! and my second problem is that in the mentioned table 'Equipement' there is no duplicate value !

Is anyone able to help me on that matter ?

Thanks

1 ACCEPTED SOLUTION
collinq
Super User
Super User

Hi @CyrilleC ,

 

I am wondering about the timing of the data and the timing of the refresh.  Let's assume for a moment that the error message is correct - that there is a duplicate in "Equipmente".  HOWEVER, when you go look, there is not a duplicate.  I have seen this before in data sources where the timing is a bit interesting or where the data source itself does in fact have a duplicate, but only for a little while.  This seems to happen a lot with ERP systems in my opinion.

When I encounter this problem and then immediately hit refresh again or do a search by myself, there is rarely a duplicate that I can find.  So, it is all about timing in my experience where, for whatever technical reason, there actually is a duplicate in the field, even if only for a short time period.  So, when this happens I look at my timing and for what the source is and where it might happen.

 

In your case, if you go to the data source for the Equipmente table, you might find that when something is added or moved or deleted from that table it creates a temporary record.  And, that temporary record is "there" when you run the refresh and that is why you see it sometimes, but not other times.

 

Also - I have run into issues where humans make a mistake and the data source allows a duplicate but then later they fix it and so it is gone by the next refresh.  So, not always technical but the scenario you stated is one that I have run into a number of times in the case as I explained above.




Did I answer your question? Mark my post as a solution!

Proud to be a Datanaut!
Private message me for consulting or training needs.




View solution in original post

2 REPLIES 2
collinq
Super User
Super User

Hi @CyrilleC ,

 

I am wondering about the timing of the data and the timing of the refresh.  Let's assume for a moment that the error message is correct - that there is a duplicate in "Equipmente".  HOWEVER, when you go look, there is not a duplicate.  I have seen this before in data sources where the timing is a bit interesting or where the data source itself does in fact have a duplicate, but only for a little while.  This seems to happen a lot with ERP systems in my opinion.

When I encounter this problem and then immediately hit refresh again or do a search by myself, there is rarely a duplicate that I can find.  So, it is all about timing in my experience where, for whatever technical reason, there actually is a duplicate in the field, even if only for a short time period.  So, when this happens I look at my timing and for what the source is and where it might happen.

 

In your case, if you go to the data source for the Equipmente table, you might find that when something is added or moved or deleted from that table it creates a temporary record.  And, that temporary record is "there" when you run the refresh and that is why you see it sometimes, but not other times.

 

Also - I have run into issues where humans make a mistake and the data source allows a duplicate but then later they fix it and so it is gone by the next refresh.  So, not always technical but the scenario you stated is one that I have run into a number of times in the case as I explained above.




Did I answer your question? Mark my post as a solution!

Proud to be a Datanaut!
Private message me for consulting or training needs.




Hello,

It seems to work! thanks a lot.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.