When creating a request from a duplicate identification batch, the selected master record is not being saved on the resulting request.

(Doc ID 2313441.1)

Last updated on OCTOBER 17, 2017

Applies to:

Oracle Customer Data Management Cloud Service - Version 11.12.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.12.1.0.0 version, Data Quality, Customer Hub

ACTUAL BEHAVIOR
---------------
When creating a request from a duplicate identification batch, the selected master record is not being saved on the resulting request.

EXPECTED BEHAVIOR
-----------------------
The selected master record should be saved and used for the merge.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to Sales Cloud application
2. Navigate to Customer Data Management > Duplicate Identification
3. Select Create Duplicate Identification Batch task and create a batch on Organization and Schedule
4. Navigate to Customer Data Management > Duplicate Identification
5. Select Manage Duplicate Identification Batches task and click on the Batch Id
6. Click on the Duplicate Id
7. Click on Create Request button and select type as Merge and click OK
8. Change the master record and Submit
9. Navigate to Setup and Maintenance > Task: Run Request Dispatch Job > Go to Task
10. Navigate to Customer Data Management > Duplicate Resolution
11. The master record has reverted to the default (it is no longer the one selected when creating the request)

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot select the master record when creating a request from a duplicate identification batch.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms