Parent Check for Merging Records in Dynamics 365 CRM | Power Apps

In case you ever tried to Merge records in Dynamics 365 CRM and it failed, you’d usually see the below error –

The error reads – “Unable to merge because sub-entity will be parented differently. You can disable the parent check prior to execution as part of Merge dialog.“

Let’s see why this error occurs and how to solve this.

Scenario

This scenario occurs because the records you are trying to Merge had different Parent records already.
Example –

1. Notice the below records selected for Merging –
   The Contacts to be Merged already belong to different Parent Account
   
2. And when you select them for Merging using the Merge button upon their selection.
   
3. You’ll also be given Parent Checking selected by Default.
   
4. This is what causes the error.
   Now, if they either had the same Parent or one of them doesn’t have a parent, this won’t appear and they’ll be Merged.
   
5. Now, they’ve been correctly Merged and only 1 record exists.
   

Hope this helps!

Here are some Power Automate posts you want to check out –

1. Select the item based on a key value using Filter Array in Power Automate
2. Select values from an array using Select action in a Power Automate Flow
3. Blocking Attachment Extensions in Dynamics 365 CRM
4. Upgrade Dataverse for Teams Environment to Dataverse Environment
5. Showing Sandbox or Non Production Apps in Power App mobile app
6. Create a Power Apps Per User Plan Trial | Dataverse environment
7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
8. Co-presence in Power Automate | Multiple users working on a Flow
9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
11. Call a Flow from Canvas Power App and get back response | Power Platform
12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
14. Asynchronous HTTP Response from a Flow | Power Automate
15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

This post was originally published on this site