What we're doing to make data deployments more successful

Tom Smith on April 5th 2019


Errors during data deployments can be confusing to say the least. Here's some of the recent changes which will help you deploy your data.

Gearset makes deployment errors clearer

The error messages from Salesforce's API often aren't clear about why an error has happened or how you can fix it. One of the most common errors we see is DUPLICATE_EXTERNAL_ID.

DUPLICATE_EXTERNAL_ID:ExternalId: more than one record found for external id field: 
[0011t00000Mdx67AAB, 0011t00000MdwoiAAB, 0011t00000GG3I4AAL, 0011t00000MxOKaAAN]

Gearset now explains why errors have happened and what you need to do to fix them. For example, I've tried to upsert the Account object using the Name field as the external id. Unfortunately several records in the target have the same name, which causes the DUPLICATE_EXTERNAL_ID error.

Gearset's explanation of the DUPLICATE_EXTERNAL_ID error

We've also written help docs which explain the errors in more detail.

Gearset explains what's causing the error and how to fix it

Honesty about whether the deployment was successful

We'll be clear about what happened during a deployment.

If we've deployed every single record then we'll say the deployment was successful.

All records were successfully deployed to the target

If we've deployed some, but not all records, then we'll say so.

The deployment finished but some records couldn't be deployed

The deployment stopped because of an error but some records were deployed

If we haven't deployed any records, that's what we'll say.

The deployment finished but no records couldn't be deployed

The deployment stopped because of an error and no records were deployed

Any suggestions?

If there's other errors which you think could be clearer then let us know! Email us at [email protected] or leave a message in the in-app chat. We'll fix the error or provide more information about it to help you finish your deployment.

Ready to get started with Gearset?

Start free trial