All Collections
Gearset for data sandbox seeding
Resolving data deployment errors: missing related records
Resolving data deployment errors: missing related records

Troubleshooting errors when attempting to deploy records with missing related records in the target org.

Ben Thompson avatar
Written by Ben Thompson
Updated over a week ago

When deploying or restoring data to Salesforce, you may encounter an error that reads:

ENTITY_IS_DELETED:entity is deleted:--



This article explains why these errors occur, and how to resolve it.

The cause

This error message indicates that a record Gearset is trying to deploy to the target org has a related record that does not exist there yet.

The INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY error can occur when the record has been permanently deleted from the Recycle Bin or if the record never existed in the first place, however this error can also occur for other reasons, such as permission issues.

Fixing the issue

If you are restoring a backup, Gearset may be able to fix this issue for you using our data problem analyzers, using the Add missing parents button.

While the ENTITY_IS_DELETED:entity is deleted:-- error occurs when the related record is in your recycle bin, the INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY can occur when the record does not exist in your org (including the recycle bin) or if the user does not have sufficient permissions to see the related record

Another potential fix for both the ENTITY_IS_DELETED and INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY errors is to remove the offending field from the deployment or restore. This can be an effective solution if the field is not critical to the operation of the data being deployed or restored.


Did this answer your question?