Select a Record Matching Method

To specify a record matching method:

From the Next-Gen Data Set Editor, in the Object view, click the Settings tab.
Select the Record Matching Method to use during deployment. All records require use of a Prodly virtual external ID, Prodly composite external ID, or Salesforce external ID. Refer to the topic on determining the best record matching method for more information about Prodly’s custom upsert capabilities. The following Records are available:

Virtual External ID – Manages inserts and upserts by tracking IDs through the custom, proprietary Prodly virtual external ID manager, eliminating the need for standard Salesforce external IDs. The VEID manager works independently for each control org.
Standard Upsert – Performs the action of a standard Salesforce upsert. If the SOQL query returns more than one matching record, Prodly generates an error. If one record matches, Prodly updates the record. If no record matches, Prodly inserts a new record.
Match First Found – If the SOQL query returns more than one matching record, Prodly updates the first record. If one record matches, Prodly updates the record. If no record matches, Prodly inserts a new record.
Skip Duplicate – If the SOQL query returns more than one matching record, Prodly skips that source record and does not insert or update any of the matching records in the destination org. If one record matches, Prodly updates the record. If no record matches, Prodly inserts a new record.

The default record matching method at the time of installation is Virtual External ID. To change the default record matching method, navigate to the Data Set object in Object Manager and update the default picklist value for the Upsert Record Handling field.

Setup > Objects and Fields > Object Manager > Data Set > Fields & Relationships > Upsert Record Handling

</aside>

Determine the Best Record Matching Method for Your Use Case

Prodly provides powerful upsert features which take the standard Salesforce upsert functionality to a whole new level. The following sections describe each approach. In Prodly, you need to specify the approach for each data set object independently.

Virtual External ID (VEID)

Prodly virtual external ID (VEID) allows you to upsert records without having to know or define any Salesforce external ID fields or specify fields in Prodly as part of Prodly composite external IDs. During initial deployment to an empty destination org, the VEID manager captures source record IDs and creates associations between source and destination record IDs. Then, the Prodly VEID manager tracks any subsequent deployments of the same record IDs between any of your orgs.

If you are not starting with an empty destination org, refer to VEID Setup During A Development Cycle before proceeding.

</aside>

New users have a much quicker time to deployment, less ramp up effort, less frustration, and reduced learning curve. Experienced users can simplify their data set model and streamline their deployment performance.

To use VEID, simply select Virtual External ID from the Record Matching Method picklist on the Settings tab in the data set Object view and perform a deployment.

The VEID manager cannot match differing IDs of data records you create in an org by any method (such as a data loader or manual entry) other than a Prodly VEID org-to-org or version-control deployment. For the VEID to be successful, the IDs of records created with a sandbox refresh, sandbox cloning, or tools other than Prodly VEID must match in your source and destination orgs. Refer to the links in this note for more information.

</aside>

Composite External IDs (CEID) / Standard Upsert

Performs the action of a standard Salesforce upsert. If the SOQL query returns more than one matching record, Prodly generates an error. If one record matches, Prodly updates the record. If no record matches, Prodly inserts a new record.

Prodly allows you to concatenate fields to create composite IDs, rather than rely on traditional Salesforce external IDs. Prodly provides the following expanded capabilities for creating composite external IDs: