You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you find duplicate records you can combine them into one using the <xref:Microsoft.Dynamics.CRM.Merge?text=Merge Action>.
18
+
When you find duplicate records, you can combine them into one using the [Merge Action](xref:Microsoft.Dynamics.CRM.Merge).
19
19
20
20
> [!NOTE]
21
21
> Only the following entity types can be merged:
@@ -34,11 +34,11 @@ Merge is an unbound action that accepts four parameters:
34
34
|---------|---------|---------|---------|
35
35
|`Target`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|The target of the merge operation.| No|
36
36
|`Subordinate`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|The entity record from which to merge data.| No|
37
-
|`UpdateContent`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|Additional entity attributes to be set during the merge operation.| Yes|
37
+
|`UpdateContent`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|More entity attributes to be set during the merge operation.| Yes|
38
38
|`PerformParentingChecks`|Boolean|Indicates whether to check if the parent information is different for the two entity records.| No|
39
39
40
-
Merging will move any useful data from the `Subordinate` record to the `Target` record. Any existing data in the `Target` record will not be overwritten. Then the `Subordinate` record is deactivated.
41
-
To perform this operation the caller must have privileges and access rights to both the records identified as the `Target` and `Subordinate`.
40
+
Merging moves any useful data from the `Subordinate` record to the `Target` record. Any existing data in the `Target` record aren't overwritten. Then the `Subordinate` record is deactivated.
41
+
To perform this operation, the caller must have privileges and access rights to both the records identified as the `Target` and `Subordinate`.
42
42
43
43
Use a POST request to send data to merge records.
44
44
This example merges two account entity records while updating `accountnumber` property of the record that will remain after the merge.
@@ -85,18 +85,18 @@ OData-Version: 4.0
85
85
86
86
The merge behavior for `incident` (case) table is different from `account`, `contact`, or `lead` tables.
87
87
88
-
- The `UpdateContent` parameter data is not used.
88
+
- The `UpdateContent` parameter data isn't used.
89
89
- Merge is performed in the security context of the user
90
90
91
-
Merge operations for other tables are performed with a system user security context. Because incident merge operations are performed in the security context of the user, the user must have the security privileges to perform any of the actions, such as re-parenting related records, that are performed by the merge operation.
91
+
Merge operations for other tables are performed with a system user security context. Because incident merge operations are performed in the security context of the user, the user must have the security privileges to perform any of the actions, such as reparenting related records, that the merge operation performs.
92
92
93
-
If the user merging records doesn't have privileges for all the actions contained within the merge operation, the merge operation will fail and roll back to the original state.
93
+
If the user merging records doesn't have privileges for all the actions contained within the merge operation, the merge operation fail and roll back to the original state.
94
94
95
95
### See also
96
96
97
97
[Use Web API actions](use-web-api-actions.md)<br />
0 commit comments