Object Mapping is a process of defining the relationship between objects and entities in the Revenue Lifecycle Platform (RLP). The Object Mapping feature enables you to establish a correlation between the properties of objects and data structures. 

The initial list of objects to be synced is gathered from the tenant profile and displayed on the Object Mappings page. When you need to add new objects or fields to the sync or update the existing data structure, you can do so from the Data Sync UI on the Conga Platform. When adding new objects or managing existing objects, you can also select which fields to include or exclude from the sync operation.

You can not only map target fields to source fields but also transform target field values to match the format the Conga platform can handle if they are written differently or in an incompatible format.

You must set up your data synchronization infrastructure before object mapping. For more details on configuring data sync infrastructure, see Getting Started with Data Sync.

Object and field mapping for out-of-the-box (OOTB) objects is automatically performed as a part of customer onboarding.

To create object mapping

  1. Log in to the Conga Platform as an admin user.
  2. Click the App Launcher () icon from the top-left corner > Admin Console > Data Sync. The Mapped Objects for Data Sync page appears. 
  3. Click Create Object Mapping. A Create Object Mapping page appears.

  4. Enter values in the following fields:

    FieldDescription
    Source Object NameEnter the source object name.
    Target Object NameEnter the name of the target object that you want to map to the source object.
    SequenceEnter the sequence to indicate how important an object is. When syncing data, the system considers this number to decide which objects should be synced first.
    Sync API PathEnter the relative API path to invoke the custom API during data sync.
    Source Filter Criteria

    Enter the source system name for filtering out the records. For example, Salesforce.

    Category

    Select the application to which the object belongs, such as CLM, CRM, CPQ, etc.

    Sync Direction

    Select the direction of sync from the dropdown list:

    • Forward: Near Realtime from Salesforce to RLP
    • Reverse: Near Realtime from RLP to Salesforce
    • ETL: Extract, Transform, and Load through Data Sync.
    Custom Query

    Enter the query, including fields and criteria-based filters, to retrieve specific records. It is useful for the Postgres system as a source.

    Source Type

    Select the type of source system a data sync establishes a connection with. It supports Salesforce and Postgres at the moment.

    Skip Delete Sync?

    Enable this toggle to skip the synchronization of deleted records from the source object to the target object. By default, this feature is turned off. For an incremental sync, if a record gets deleted in the source object, the corresponding record must be removed from the target object.

    Is Protected

    Enable this toggle to prevent any modifications to the object and mark it as an OOTB schema object mapping.

    Is Enabled?

    Enable this toggle if you want the system to consider the object when syncing data.

    This applies to manual data sync. In the case of scheduled data sync, it considers the specific objects you have chosen when creating a sync schedule. For more details on scheduling data sync, see Scheduling Data Sync.

    Is Document Sync Required?

    Enable this toggle to sync the documents. This is only for the CLM application documents.

    Is Translation Object

    Enable this toggle to sync translation data of multiple languages used on the source platform. For more information, see Translation Sync.

    Is Complex Array Type?

    Enable this toggle to indicate that an object supports the Complex Array type. Once enabled, you must specify values for the Complex Array Type Field Name and Complex Array Parent ID Field Name from the platform schema.

    This is useful for the Approvals use cases.

  5. Click Save. A new object mapping is created. Next, you need to map the source objects' fields to the target objects' fields.
    1. Click on the required Object Mapping from the list > click Create Field Mapping.
      The Field Mappings page appears.

    2. Enter values in the following fields.

      FieldDescription
      Source Field NameEnter the keyword to search and select the source field name.
      Source Field TypeEnter the source field type.
      Target Field NameEnter the keyword to search and select the target field name that you want to map to the source field.
      Target Field TypeEnter the target field type.
      Target Lookup Object NameEnter the name of the lookup object if the target field is lookup.
      Rule NameSearch and select the rule name used to execute the specific transformation name that is needed as part of data sync while bringing data from the source to the destination system.
      Is Image Field

      Enable this toggle to indicate that a field is intended to store the image information in URL format.

      Is ID ColumnEnable this toggle to mark a field as the Primary ID field for the associated object. This is useful for the Conga Contract use cases.
      Is Primary Name FieldEnable this toggle to mark a field as the Primary Name Field for the associated object. This is useful for the Conga Contract use cases.
      Is Reverse Sync Enabled

      Enable this toggle to indicate that a field is a part of transaction data that needs to be synced from the platform to an external system.

      Some of the objects and fields have limitations for reverse sync. For more information, see Limitation for Reverse Sync.

      Is Enabled?Enable this toggle if you want the system to consider the field when syncing data.

    3. Click Save. A new field mapping is created for the object. 

      You might encounter field data that are written differently or in a format that doesn't match what the Conga Platform can work with. In that case, you can convert source field data into a format that matches the requirements of the Conga Platform. For more information, see Transforming Field Values.

To edit object mapping

  1. Log in to the Conga Platform as an admin user.
  2. Click the App Launcher () icon from the top-left corner > Admin Console > Data Sync. The Mapped Objects for Data Sync page appears with a list of objects. 
  3. Click the More () icon next to the object. 
  4. Click Edit. 
  5. Edit the fields as required and click Save.

Similarly, you can edit field mapping.

You can only modify synced object mappings.

To delete object mapping

  1. Log in to the Conga Platform as an admin user.
  2. Click the App Launcher () icon from the top-left corner > Admin Console > Data Sync. The Mapped Objects for Data Sync page appears with a list of objects. 
  3. Click the More () icon next to the object. 
  4. Click Delete.

Similarly, you can delete field mapping.

You can not delete if the object mapping is not synchronized and marked as Is Protected.