Notifications
Announcements
No record found.
Hi,
I have developed a data entity to use it with excel ad-in. This entity will be used to update few fields ( e.g sales figures ). While testing this data entity with excel ad-in it worked in some cases and for some it give an error "Original data contains duplicate entries". I'm not able to figure out what is the cause of this. Because for some records it works fine and for some it doesn't. It is not consistent. Record giving error doesn't seems to have any issue as it can be updated from front end or from SQL. I have checked the keys on the data entity and there are no duplicates. I was not able to find solution to this error although there were few posts on the same issue. Please suggest how can I avoid / fix this error.
Hi Pranay,
In this case, you need to check the entity key. This will determine what will be the primary key for the entity. If you need help, you have to provide some more information about the entity and the data you try to publish.
Please verify if all the scope values are filled in Excel before publishing it.
Thanks,
Sheela
Dear Andre,
My data entity is base on a custom table developed by ISV partner. I'm using same fields in the data entity keys which are on the table's Primary index. I observed that when I filter the records with contract ID and then make changes and publish the publish is successful. But when I publish for multiple contracts at once it doesn't work.
Entity is based on a custom table which stores customer sales figures. Following fields are available in the entity Contract ID, Lease Line ID, From date, To date, Product category Name, Billing type, sales type, Line number, Transactions and sales figure. Out of which only transactions and sales figures are allowed to be edited and updated and all the other fields are read only.
Are any of the editable fields part of the entity key?
Hi Nikolaos,
No, only read only fields are part of the entity key.
When this is part of an ISV solution, I would suggest to contact the ISV vendor to check what might be wrong here.
Thanks for the response. This issue was indeed because of the data entity keys. I managed to resolve it by addidng the correct keys in entity keys and entity fields.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 664 Most Valuable Professional
André Arnaud de Cal... 522 Super User 2025 Season 2
Sohaib Cheema 303 User Group Leader
