When using the Data Loader to perform bulk project uploads, the system currently allows duplicate project records to be created if existing projects are unintentionally included in a new upload file. There is no built-in validation or safeguard to prevent duplicates based on common identifiers such as Project Name or External ID unless the user explicitly uses PK-based updates.
This behavior increases the risk of data integrity issues, especially for customers who perform recurring bulk uploads and manage large project portfolios.
Current Behavior:
-
Data Loader accepts rows for project creation even if a project with the same Name or identifier already exists.
-
Preventing duplicates relies entirely on manual validation or file preprocessing by the customer.
-
There is no configurable option to block or warn users when duplicate projects are detected during upload.
Desired Behavior:
Introduce an option to detect and prevent duplicate project creation during bulk uploads by:
-
Validating against Project Name and/or External ID
-
Providing a configurable setting (e.g., “Reject duplicates” or “Warn only”)
-
Failing or skipping rows that match existing projects instead of creating duplicates
Business Value:
-
Improves data integrity and trust in bulk upload processes
-
Reduces rework and cleanup caused by accidental duplicate creation
-
Simplifies recurring uploads for customers
-
Aligns Data Loader behavior with common enterprise data governance expectations
Customer Impact:
This enhancement has been requested by customers actively using Data Loader for recurring project imports and would significantly improve usability and reliability.