Loading

Cloning a Record in Salesforce Lightning Experience Copies the Original Created Date to the New Record

Date de publication: May 4, 2026
Description

When users clone a record in Salesforce Lightning Experience, the Created Date of the original record may be copied to the newly cloned record instead of reflecting the actual date and time the clone was created.
This behavior occurs when the user performing the clone has the "Set Audit Fields upon Record Creation" permission enabled on their profile or permission set. Salesforce Lightning Experience uses the API to create records, and audit fields such as Created Date can be set by users who have this permission when creating records via the API.

Résolution

Why This Happens

When a user with the "Set Audit Fields upon Record Creation" permission clones a record in Lightning Experience, Salesforce uses the API to create the new record. Because this permission allows audit fields (such as Created Date) to be set via the API, the original Created Date is carried forward to the cloned record as part of the API record creation process. This is expected behavior for users with this permission.

How to Prevent This

To ensure that cloned records have a Created Date that reflects when the clone was actually created, do not grant the "Set Audit Fields upon Record Creation" permission to users who will clone records in Lightning Experience. Review your profiles and permission sets and remove this permission from any user who does not require it for a specific administrative purpose.

Numéro d’article de la base de connaissances

000384664

 
Chargement
Salesforce Help | Article