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.
