Salesforce Docs Portal

Seeding Limitations for Salesforce

When working with the Seeding app, take note of these points.

The Seeding application limitations affecting a Salesforce data environment are:

  • The application imposes limits on the number of object records that can be seeded. When a record limit is exceeded during data retrieval from the seeding source, the seeding job is canceled. The limits imposed per seeding job are as follows:
    • For seeding into a sandbox:
      • Maximum number of records cannot exceed 20M
      • Maximum number of ContentVersion records cannot exceed 50K

      Exceeding either one of these two limits results in seeding job cancellation.

    • For seeding into a Production org:
      • Maximum number of records cannot exceed 10K
  • The application doesn't support the following data:
    • Big objects - not supported and not seeded
    • Calculated fields (formula)
    • Chatter objects (FeedComment, Feed Attachment, etc.)
    • External objects - objects that map to data stored outside your Salesforce org
    • Geolocation fields
    • Tags
  • The application doesn't support the seeding of the following Salesforce objects:
    • ActionPlanTemplateVersion
    • CaseArticle
    • Group
    • Queue
    • VoiceCall
  • Assets with sharing enabled: To seed an Asset object, either an AccountId or ContactId is required. (Salesforce default sharing setting for Assets requires a parent account and/or contact to be defined). If this restriction was removed and the default Asset sharing setting was changed, the Seeding application can't seed it.

The above limitations are in force regardless of the type of seeding template (Nodes or Levels) that is used in a seeding job.

Seeding Limitations of the Levels Template

Levels templates have the following, additional seeding limitations:

  • Attachments are skipped. They are neither seeded nor replaced with dummy files.
  • Content Documents are skipped. They are neither seeded nor replaced with dummy files.
  • Reducing batch size for a Levels template is not supported.
  • Although mandatory parents are automatically added to any object in the hierarchy, non-mandatory parent objects can only be added to a root object.
  • Using a Levels template, you cannot seed the following objects:
    • AgentWork
    • Calendar
    • FeedItem
    • User