Perform successful data seeding jobs when you follow best practices to make sure object relationships and metadata are configured correctly.
- Review object relationships to ensure you have a true understanding of your schema and the objects you are planning on seeding before actually seeding. This will save you failed seed attempts and give you the highest probability of a successful seed when creating a seeding template.
- Before seeding data to a destination org ensure that the metadata in the destination org is optimized to allow the seeding of records. This means that if you are attempting to replicate older records, ensure the record types, picklist values and dependencies are enabled to allow the seeding of records, if not you encounter Salesforce errors.
- When a template contains a root object and its descendants, there is no need to select a descendant again as a root object, unless you specifically need to seed records that are not part of the root subset. Note that records that are also part of the subset are identified and will not be seeded again to prevent duplications.
- There is no need to apply the same filters to the child objects that you applied to the root object, as it will automatically only bring in the child object records specifically related to the records of the main object selected as root.
-
User Objects
- During a seeding job, User object records are auto-cloned to prevent any permission errors
while seeding. Therefore, there is no need to manually add the User object to the template:
- Standard users created via Salesforce during a refresh already reside in the destination, and have the same ID as in the source, are identified and mapped automatically.
- Other users are mapped by email (business id).
- Users that exist in the source org but are missing from the destination org are mapped
to the authenticated user.
Tip If you want missing users to be added to the destination, add the User object to the template being used for the seeding job. Adding the User object is only available for Nodes templates. - Nevertheless, there are a few types of users that will not be auto-cloned, as they do not affect the seeding process and are available for manual selection from the list. These users are actually contacts that are linked to user records and relevant for support cases: Owner and Case team.
- During a seeding job, User object records are auto-cloned to prevent any permission errors
while seeding. Therefore, there is no need to manually add the User object to the template:
- You may need to add an object multiple times in different locations in the same template to ensure the relationship is kept between all the objects in the template. Having one object appear multiple times in a template will not cause duplicates as the tool is smart enough to check for duplicates as it seeds records into the destination.
- When seeding Circular Related objects you must select the main object and then add the child both as a parent and a child of the main object. This ensures that the circular relationships are also created when seeding.