Gearset’s data deployment tool allows you to seed data from any org to another org, and it’s designed to be user-friendly and straightforward to use. However, we understand that it’s not always easy to use due to the data model and the cryptic error messages.
When users hit errors, we want to understand and help. These are the background information that our team needs to have, to best understand the scenario and to help.
Which object(s) API names are you trying to deploy? How are these objects related? It’s tempting to want everything in one go, but is there a way we should be breaking down a large task into smaller manageable chunks?
What primary objects are being selected on the
Configure data deploymentpage?
And what filter setting do you have in the
Configure filtersection?What related objects are selected on the
Select related objects and deployment methodspage?
Once deployed what error is logged, on what object?
Which source record IDs are being flagged as erroring?
(Here is an example of
Accountrecord ID0018d000004RD1gAAGbeing the record that is causing the error.)
Or if the results are unexpected, what do you expect to see, and what do you see?
What is the deployment results URL?
If you can provide this information in the in-app chat, our support team will be able to have a good view of what steps you’ve taken and how best to proceed.