The core issue arises from upgrades from the ESG Reporting public preview to GA. The root cause is that there are manually created records in certain entities with names that match the new default data introduced in the ESG solution. This results in a conflict with the natural key constraint during import, affecting the following entities:
To resolve this, duplicate records must be identified and removed before proceeding with the import.
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 Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Abhilash Warrier 60 Super User 2025 Season 2
Lea Kraus 16
Joke Laukens 16