DCR Outbound process fails for record with 'FAILURE - responseStatus: FAILURE: DUPLICATE_KEY: no message'
Data Change request is sent to Network without the response being written to the DCR record in CRM. This causes the DCR_External_Id_vod__c field to not be populated with the expected Task Id, and the Status_vod__c field is not updated to Pending_vod. As a result, the DCR is sent with every DCR Outbound Job, and is never updated using a DCR Inbound Job.
Impacted DCRs need to be manually updated with the DCR_External_Id_vod__c field populated with the Network Task Id for the Change Request, and the Status_vod__c field updated to Pending_vod.
When this is done, the DCR Outbound errors no longer appear, and the DCR processing is completed on the next DCR Inbound job once the Change Request has been processed in Network.
Manually finding Task Ids in Network needs to be performed for individual cases. The Network Task Id for Change Requests can be found by navigating to the related account in Network and pulling the Task Id from the correct Change Request on the Account. For Add Requests, the Task Id can be found by searching Network for Tasks with the same Created Datetime as the DCR in CRM.
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.