Salesforce Data Errors

Error Message: DUPLICATE_VALUE / DUPLICATES_DETECTED

Error Description: The records in the organization already exist.

Example: The price definition record already exists in this price book.

Error Resolution: Validate if it is a duplicate, remove it from the destination, and restore it from the backup. OR Exclude the record from the Restore & Seeding.

Error Message: DUPLICATE_USERNAME

Error Description: The username already exists in this Salesforce or another organization.

Error Resolution: Change the username (does not require matching the user's email address) before restore. OR Clear the user object checkbox to avoid restoring it. Usernames must be unique across all Salesforce organizations. OR Ignore the error if the user already exists.

Error Message: UNABLE_TO_LOCK_ROW

Error Description: Records are created or updated in Salesforce concurrently and have familiar parents on which these child objects acquire lock during modification.

Error Resolution: Configure the restore template batch size:

1. Navigate to the data restore template detail page.

2. Go to Restore & Seeding Settings tab → Batch Size → Decrease the batch size (reduces probability of this error). OR Enable Process Serial and click Save (speed might decrease slightly).

Error Message: REQUIRED_FIELD_MISSING

Error Description: Missing mandatory field in an object.

Example: Attempting to add a campaign member where either the member ID or the campaign ID is null.

Error Resolution: Verify the mentioned member or campaign ID is present. Check the source organization to verify the missing fields or make them optional on the destination Salesforce organization.

Note: If the fields are backed up and the template is not configured to exclude these fields, contact support.

Error Message: INVALID_FIELD

Error Description: Error caused due to invalid input in fields.

Examples:

1. (RelatedRecordId) Looks like the selected user does not have permission to be a service resource. Your Salesforce admin can help with that.

2. (IsActive) The Service Resource cannot be activated because its related Service Crew has no active Service Crew Members.

3. (IsActive) MISSING LABEL PropertyFile - val noActiveMembers not found in section ServiceResourceErrors.

4. (Type) Cannot directly insert FeedItem with type TrackedChange (Due to limitations with Salesforce we can't insert FeedItem object of type TrackedChange).

Error Resolution: Manually exclude the fields in the Account Object from the Restore & Seeding settings located under the Restore & Seeding tab.

Error Message: INVALID_OPERATION

Error Description: The DML operation (for create/update/delete) is not supported. Examples:

1. (AssociationCause) An object territory association cannot be created or deleted with Territory Assignment Rule association cause.

2. Cannot create, update, or delete Feed Attachment.

3. Cannot create, update, or delete Feed Attachment of type InlineImage.

Error Resolution: ObjectTerritory2Association cannot be copied via application; once the parent object and its territory are loaded to the destination organization, customers can associate them with Salesforce in bulk. You can read, create, update, or delete a feed attachment only if you have corresponding access to the associated FeedItem.

Error Message: INVALID_CROSS_REFERENCE_KEY

Error Description: Error caused by adding invalid reference values to a field of the failing restore object. May also occur when field values are invalid for the user or the user does not have access to the field value.

Error Resolution: Common scenarios and resolutions: Verify the authenticated user has correct permission to access the Record Type. Error messages include: (RecordTypeId) Record Type ID: this ID value is not valid for the user: {userId}. (RecordTypeId) Party Record Type: this ID value is not valid for the user:{userId}. Sometimes the user ID is empty. Provide permission to users for this recordType. Assign user record types in permission sets. Check for correct reference value. If the field is Record Type, confirm if the same is enabled for the user.

Error Message: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY

Error Description: Error caused due to apex triggers.

Error Resolution: Disable or fix the apex code when objects are created/updated.

Error Message: STORAGE_LIMIT_EXCEEDED

Error Description: Storage limit exceeded.

Error Resolution: Clear storage from the organization to allow further restore/copy to the destination organization.

Error Message: FIELD_CUSTOM_VALIDATION_EXCEPTION

Error Description: Some triggers or validation checks are enabled.

Error Resolution: Take necessary action as per the error reason shown by Salesforce.

Error Message: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY

Error Description: Insufficient access permissions on cross-reference ID.

Error Resolution: If the error is reported in the RecordId field and the Record ID does not exist in the destination, restore the record ID and retry the restore of the failed object. If it exists, check the user's permissions to the record.

Note: If the error is reported on any other field, contact support.

Error Message: CANNOT_UPDATE_CONVERTED_LEAD

Error Description: Salesforce does not allow updating data of a converted lead.

Error Resolution: Use the "Converted" EQUAL TO "No" filter to exclude the converted leads.

Error Message: INVALID_FIELD_FOR_INSERT_UPDATE

Error Description: Some fields are prohibited considering the object type. Example: Custom/Non-person Accounts do not require the middle name and suffix, but the object schema might have these fields due to the presence of a person account.

Error Resolution: Manually exclude such fields from the data settings located under the Restore & Seeding tab.

Error Message: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST

Error Description: The destination org does not have the picklist values in the backup or source organization.

Error Resolution: Create picklist values that match the values in source org or backup.

Error Message: UNSUPPORTED_APEX_TRIGGER_OPERATION

Error Description: Error caused while updating many events like inserting, deleting, or updating recurring events or tasks.

Error Resolution: Disable the trigger metadata before restoring. For more information, see Help And Training Community.

Error Message: FIELD_INTEGRITY_EXCEPTION

Error Description: This issue is caused when we try to create/update records with incorrect fields for an object.

Examples:

Scenario 01: Task Relations (Task_Id) "You can only add up to one relation" - TaskRelation objects prohibit adding multiple relations. Adding Account, Campaign, and other standard or custom objects will cause this issue.

Scenario 02: Mismatched integration value and ISO code for field: Billing Country Code - ISO code field issues - either remove the field next time you copy or insert a proper one.

Scenario 03: (ConvertedAccountId) Converted Account empty for a Converted Lead. This error happened because the Converted Lead in your source tool doesn't have the following fields populated:

1. Converted Account ID

2. Converted Contact ID

3. Converted Opportunity ID.

Error Resolution: Review the error message and analyze the error from Salesforce. The error messages provide steps/hints required to fix the issues.