--- schema_version: "1" id: acabe580fc02670d57be933d77fd487997ee287ac4776a7ed47ff0fb7e405929 title: Seeding for Salesforce FAQs collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/seeding_o_faqs.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.seeding_o_faqs.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a474666521da4f7cecc00afa4eeadd1395639c04e2fc2c383823befd5c51de7e description: If you encounter issues related to Seeding for Salesforce, the answers to frequently-asked questions can sometimes help you. products: - Security - Salesforce Platform release: "264" --- # Seeding for Salesforce FAQs If you encounter issues related to Seeding for Salesforce, the answers to frequently-asked questions can sometimes help you. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/images/icon_note.png) Note (Own) authenticated user is the Salesforce user that the Seeding application uses to access a specific Production org or a specific sandbox. ## Can I seed metadata between environments? No. Seeding of metadata is not supported. ## What metadata is modified in the Destination Org during seed? If the user selects to disable Validation Rules for a seeding job, Own automatically disables all possible Validation Rules, Workflows, Triggers (except for triggers that are part of managed packages), and Processes on the destination environment during seeding, and automatically reenables them upon seeding job completion. Both activities require a “metadata deploy.” Keep this in mind if you’re seeding to sensitive environments. ## What happens with records owned by Portal/Community users? When seeding records owned by portal/community users, the system replaces the owner of the records with the Own authenticated user for the destination service. ## What happens with records owned by Inactive Users? In the case where the Own authenticated user for the destination has permission to UpdateWithInactiveOwner, the records are seeded with the original owning user. Otherwise, the system replaces the records’ owner with the Own authenticated user for the destination service. ## Can we seed User records? Yes, with the exception of Portal users. For information about seeding the supported type of user, see Seeding Best Practices. ## When anonymizing as part of a seeding job, does sensitive data/personally identifiable information (PII) get to the destination sandbox? No, anonymization of the seeding source data is performed first, before any seeding source data is inserted into the destination sandbox. ## Why would I want to disable matching users? In case you want to reduce the seed time and you know that the destination contains users that also exist in the source. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/images/icon_note.png) Note Any records that are owned by users that don’t exist in the destination fail. ## Why would I disable the seeding template Advanced Settings option Auto cloned objects matching for Product2, PriceBook and PricebookEntry? By disabling this option, the seeding job skips matching these auto-cloned objects, thereby reducing seeding job processing time. You can disable the option when any one of the following conditions is true: - You know that you don’t need these objects to be seeded. - You know that these objects didn’t change in the seeding source, since being auto-cloned to the destination sandbox, when that sandbox was either created or last refreshed. ## How can I seed files? For seeding files, always add the relevant object to the template (Attachment, Document and/or ContentDocument). You can add Document object to the template, and for Attachments and ContentDocument always add their parent object. For example, if you want to seed Account’s attachments, select Account and add Attachment and/or ContentDocument objects as child objects. ## Why don’t I see my original file in the destination? By default, for both Nodes templates and Levels templates, the Seeding application seeds dummy files. During a seeding job, the original files are replaced with a dummy file that correlates to the original file type, matching it by file name. When using a Nodes template to seed ContentDocument objects, you can choose either to Seed dummy content or to Seed the real content. These options are provided in the ContentDocument Handling section of the Advanced Settings for a Nodes template. For details,see Seeding Template Advanced Setting and Seeding Attachment, Document, and ContentDocument Objects. ## Why do I see additional objects when I add ContentDocument to my template? Salesforce uses three objects to store files data: ContentDocument, ContentVersion and ContentDocumentLink. Therefore, all three need to be seeded. The actual “content” of the file is saved as a ContentVersion, and is a child of ContentDocument. ContentDocumentLink is the object that connects ContentDocument to a given record. For example, if you added a file to an Account record, the object relationships are: Account → ContentDocumentLink → ContentDocument (required parent of ContentDocumentLink) → ContentVersion (required parent of ContentDocument). ## Why do I get duplicate files while I selected the Clean and Insert seeding method (the existing files should have been deleted before seeding new files) There’s a technical limitation. ContentDocument, ContentDocumentLink, and ContentVersion objects can’t be deleted when selecting the Clean and Insert seeding method. ## An object in the seeding template continuously fails to be seeded. This object triggers many automations that I can’t disable and the insertion always fails due to timeout. What can I do to successfully seed this object? To prevent the timeout from occurring, set a lower batch size for the insertion of this particular object. When you configure the seeding job, modify batch size in the Advanced Settings tab. ## How can I reseed records that I deleted from my sandbox? If you manually deleted data from the sandbox, since it was last used as the destination of a seeding job, the Seeding application may not know about these deletions. To repopulate the sandbox with the deleted data, execute a seeding job that uses the sandbox as the destination and reindexes the sandbox. When configuring the seeding job, in the Advanced tab of the dialog, select the Update destination index option. This option causes the Seeding application to know to reinsert deleted object records. ## Why do I see errors when seeding the AccountContactRelation object? The errors that occur when seeding the AccountContactRelation object are a false positive. When you insert a non-private contact in your org that associates a contact to multiple accounts, an AccountContactRelation is automatically created by Salesforce, and its validation rules, database insertion, and triggers are executed immediately after the contact is saved to the database. When you change a contact’s primary account, an AccountContactRelation may be created or edited, and the AccountContactRelation validation rules, database changes, and triggers are executed immediately after the contact is saved to the database. Therefore, you can disregard the errors that you see, as a new object should exist in the destination and it should connect the relevant Contact and Account objects. For more details, see AccountContactRelation in the Object Reference for the Salesforce Platform > Standard Objects category. ## I added an object to my template. When trying to add a filter for that object, I notice that one or more of the object's fields is missing from the Fields drop-down. Object fields in Salesforce can be hidden from the authenticated user, if the authenticated user isn’t assigned read permissions for those specific fields. Add the missing field permissions. 1. Navigate to the Backup tab and select the relevant service. 2. In the Dashboard, a warning message is displayed advising that some fields may have failed to be backed up, due to permission issues. Click the see report link or click Permissions Report on the side menu. The Permission Report opens. 3. Search for missing file. 4. Navigate to the Options tab to verify the Authenticated User. 5. In Salesforce add the fields’ permission to the authenticated user.