Control your match processing for auto-cloned objects such as users, products, and price books within the Seeding application. Advanced settings can help prevent duplicate object records and make sure every record has a designated owner.
Any differences in the advanced settings between Nodes templates and Levels templates are described.
The Seeding application provides the following advanced settings for use with seeding templates:
- Auto-cloned objects matching: Prior to the seeding of data, the Seeding application first
matches object records between the seeding source (service) and the seeding destination
(service). The application performs this match processing for the following reasons:
- To avoid the seeding of duplicate object records
- To ensure that all records to be seeded have an assigned owner, this being either the owner assigned at record creation or, if a record has no owner, the Seeding application assigns it the Own authenticated user. This prevents the seeding of records from failing, due to them missing an assigned owner.
Auto-cloned objects matching provides you with the ability to enable/disable this match processing for the following auto-cloned objects:
- User - By default, in newly created seeding templates, auto-cloned object matching is enabled for this object
- Product2, Pricebook and PricebookEntry - By default, in newly created seeding templates, auto-cloned object matching is enabled for these objects
Note Salesforce automatically clones these objects from Production to sandbox, when creating a sandbox. - ContentDocument Handling: Provides you the ability to select the content to be seeded as
an attachment in the Destination for instances of the ContentDocument object in the Seeding
Source. ContentDocument Handling options are only available for Nodes templates. The options
are as follows:
- Seed dummy content - seed a file attachment containing fake (dummy) content. By default, this option is enabled in newly created seeding templates.
- Seed the real content - seed the real file attachment containing the authentic
content as provided in the specific ContentDocument object in the Seeding
Source.Note Limited to 50K ContentVersion records - per seeding job, the maximum number of real content records to be seeded as attachments is 50K (ContentVersion) records. If the 50K maximum is exceeded, the seeding job is canceled and the generated Seeding Report records this cancellation.
- Change default batch size - Provides you the ability to modify the default Bulk batch size for an object. The default Bulk batch size defines the maximum number of records that can be included in a record batch when Bulk API is used to seed the object's records into a Destination. Consider modifying the default Bulk batch size for an object, when seeding of that object fails due to timeout errors caused by size, triggers, or validation rule limitations.