Add or Delete Field Sync Mapping Rows

Install

Salesforce Connector for CLM and CI

package. See Set Up Salesforce Connector for Contract Lifecycle Management and Contract Intelligence.

Set Up Two-Way Connection Between Salesforce and Contract Management and Document Intelligence. See Set Up Two-Way Connection Between Salesforce and Contract Management and Document Intelligence.

You can add and delete field sync mapping rows in the

Sync Fields Form

to control which Salesforce and Contract Intelligence fields are synchronized.

You’ll receive an

Invalid mapping: destination field ‘(deleted field Name)’ is not found

error if a previously mapped field in Contract Management and Document Intelligence has been deleted or renamed. As a result, Salesforce can no longer sync data to this field.

To resolve this error, identify the invalid field in the error message and edit the existing field sync mapping row to connect the Salesforce field to the correct Contract Intelligence. Or, delete the field sync mapping row if the field is no longer needed for syncing.

Add new field mappings:

Access the

Sync Fields

tab in the Evisort Admin app.

When you are creating a new object mapping, click the

Set Object Mapping

button.

When you are editing an existing mapping, select an existing mapping row in the Sync Fields table, and click

Edit

For new mappings, select an object from the

Salesforce Object

drop-down menu and click the

New Field Mapping

button.

Select a Salesforce field and the Contract Intelligence field you want to map it to.

Delete a field mapping:

To delete a single field mapping, click the trash icon to the right of the field mapping row in the open form. After deleting the unwanted rows, click

Save

to save the updated mapping.

To delete the entire object mapping, click the down arrow in the table entry for the mapping and click

Delete

We support Salesforce Files, ContentDocument/ContentVersion, and Enhanced Notes, ContentNote, used by Salesforce orgs created after April 2016. The integration fully supports Files, including files stored in Libraries or directly associated to records.

We don’t support legacy Notes and legacy Attachments.