Skip to main content
Openprise Academy

Oracle Sales Cloud Merge Records

Updated

Pro & Enterprise

 

Purpose

Merge duplicated Oracle Sales Cloud Contact or Account records.

 

Category Location: All, System specific

 

Field Description
 Oracle Sales Cloud merge records.jpg

  1. Oracle Sales Cloud Data Target: Select the data target you've created in Openprise.
  2. Record Type: Select the object. Options are : Account or Contact
  3. Attribute which contains record Id: Select the attribute that contains the record Id.

Advanced Configurations

Oracle Sales Cloud merge advanced configurations.jpg

  1. Prioritize records to export: Select this option to prioritize which records to merge.
  2. Attribute to use for prioritization: Select the attribute that will be used to prioritize records to merge.
  3. Sorting order of the prioritization attribute: Set either ascending or descending order of the prioritization attribute.
  4. Total number of records to process: Set the total number of records you'd like to merge.
  5. Seconds to wait between polling duplicate sets: Determines how long to wait between polling a duplicate set. Depending on usage, you may want to configure delays between polling duplicate sets to avoid errors.
  6. Minutes to poll merge status of each duplicate set: Determines how long to poll for a success or failure response before Openprise moves on to the next duplicate set. If a success or failure is not obtained within the configured timeframe, the records will remain marked as “PENDING”. You will need to look in Oracle Sales Cloud to see the merge results. This is an Oracle Sales Cloud specific constraint.

Created Attributes

This task template creates the following attributes to provide information related to the merge:

op_merge_errors: contains any errors during the merge process

op_merge_merged_record_ids: contains the ids of the non-surviving records

op_merge_status: true or false

op_merge_success: yes or no

op_merge_time: date and time of the merge

op_merge_updated_related_ids: provides ids of any related objects that were re-parented

 

Tips

  • This task requires a de-duplication and merge task to run first in order to produce merged objects. This is because the Oracle Sales Cloud merge task looks for duplication groupings within the records, which is created by the de-duplication and merge task.
  • To support automated merging in Oracle Sales Cloud, we run duplicate resolution requests using Oracle Sales Cloud’s ESS trigger. This trigger processes ALL duplicate resolution requests that are actively pending, including those that Openprise did not submit. When reviewing merge results in Openprise, we will only look against Openprise submitted requests. Other submitted requests will need to be reviewed within Oracle Sales Cloud.
  • Merges in Oracle Sales Cloud are asynchronous, so we have to poll against Oracle Sales Cloud to see if the merges are successful or not. The advanced configuration section determines how we poll against Oracle Sales Cloud.

 

 

Related articles