---
schema_version: "1"
id: 99881c8c7a638cd924c0da5097c365b89fdefaa4552b697470f38c4f42edf9af
title: Disable Auto-Clone Object Matching from Your Salesforce Template
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/seeding_o_disable_auto_clone.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.seeding_o_disable_auto_clone.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6153e128f787dbe7b0b783ec95593298f410600033d750a6fd5814205ec71fae
description: Disable auto-clone object matching to speed up your seeding jobs and avoid seed failures caused by large records. When you disable auto-clone matching, you reduce processing time, especially when the destination already contains the necessary records.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Disable Auto-Clone Object Matching from Your Salesforce Template

Disable auto-clone object matching to speed up your seeding jobs and avoid seed failures caused by large records. When you disable auto-clone matching, you reduce processing time, especially when the destination already contains the necessary records.

The process to disable auto-clone objects matching from a template is the same process for both Nodes and Levels templates. In this article, we show a Nodes template example.

Auto-Clone

While creating a sandbox, Salesforce automatically clones several objects from Production to the sandbox.

To avoid creating duplicates, the Seeding application first matches the cloned object records in the source and the destination, and then skips seeding records that already exist in the destination.

## Advanced Option

User object is not visible for selection in the template as users are auto-cloned by Salesforce when creating a sandbox. An option exists for advanced users who need to seed User records that are not auto-cloned (i.e. Community Users/Partner Users).

- For Mac:
    - Hold down the Option + Command keys, you are then able to see and add User object to the template. Once added, use the filter to specify the relevant User type.
    - Enter the word user in the object field, then hold down the Option + Command keys; you are then able to see and add User object to the template. Once added, use the filter to specify the relevant User type.

- For Windows:
    - Hold down control + alt keys for Windows, you are then able to see and add User object to the template. Once added, use the filter to specify the relevant User type.
    - Enter the word user in the object field, then hold down control + alt keys for Windows you are then able to see and add User object to the template. Once added, use the filter to specify the relevant User type.

## Disable Auto-Clone

If you are aware that matching auto-cloned objects might cause the seed to fail, due to a large number of records, or you are sure that all records already exist in the destination and there is no need to run the matching step, you can disable the auto-clone matching function for the relevant object(s).

![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 If you choose to disable auto-matching and the objects are included in the template, duplicate records might be created.

1. Click the three dots on the template. The drop-down menu opens.
2. Select Advanced Settings. The Advanced Settings window opens.
3. Clear the selected options to disable auto-clone matching.
    
    When matching users, we verify that the destination org contains the source users; missing users are mapped to the authenticated user to successfully seed all records. Disabling the Users option results in a faster seed, however, seeding records where the owner does not exist, fail.
    
    If the template does not contain Product2, PriceBook & PricebookEntry objects, you can disable matching them, to shorten the seed time.
    
    By default, both options are selected. Changing (disabling/enabling) these options affect future seeds. The settings are copied when cloning a template.