Classe MergeRequest
S'applique à: CRM 2015 on-prem, CRM Online
Contains the data that’s needed to merge the information from two entity records of the same type.
Espace de noms: Microsoft.Crm.Sdk.Messages
Assembly: Microsoft.Crm.Sdk.Proxy (dans Microsoft.Crm.Sdk.Proxy.dll)
Syntaxe
'Déclaration
<DataContractAttribute(Namespace:="https://schemas.microsoft.com/crm/2011/Contracts")> _
Public NotInheritable Class MergeRequest
Inherits OrganizationRequest
[DataContractAttribute(Namespace="https://schemas.microsoft.com/crm/2011/Contracts")]
public sealed class MergeRequest : OrganizationRequest
Exemple
The following example shows how to use this message. For this sample to work correctly, you must be connected to the server to get an IOrganizationService interface. For the complete sample, see the link later in this topic.
// Create the target for the request.
EntityReference target = new EntityReference();
// Id is the GUID of the account that is being merged into.
// LogicalName is the type of the entity being merged to, as a string
target.Id = _account1Id;
target.LogicalName = Account.EntityLogicalName;
// Create the request.
MergeRequest merge = new MergeRequest();
// SubordinateId is the GUID of the account merging.
merge.SubordinateId = _account2Id;
merge.Target = target;
merge.PerformParentingChecks = false;
Console.WriteLine("\nMerging account2 into account1 and adding " +
"\"test\" as Address 1 Line 1");
// Create another account to hold new data to merge into the entity.
// If you use the subordinate account object, its data will be merged.
Account updateContent = new Account();
updateContent.Address1_Line1 = "test";
// Set the content you want updated on the merged account
merge.UpdateContent = updateContent;
// Execute the request.
MergeResponse merged = (MergeResponse)_serviceProxy.Execute(merge);
Remarques
Message Availability
Pour que ce message fonctionne, l'appelant doit être connecté au serveur.
Usage
Pass an instance of this class to the Execute method, which returns an instance of the MergeResponse class.
Privileges and Access Rights
To perform this action, the caller must have privileges and access rights on the specified entity in the SubordinateId property and privileges on the entity that is referred to in the Target property.
For a complete list of the required privileges, see Merge Privileges.
Supported Entities
Le tableau suivant montre les entités par défaut prenant en charge ce message. Pour les entités répertoriées, l'appelant doit être connecté au serveur pour que ce message soit disponible.
Entity |
---|
account |
contact |
lead |
incident |
For a description of how actions on a parent record affect child records, see Entity Relationship Behavior.
Merge incidents
The behavior of merge for incidents is different from merging accounts, contacts, or leads in the following ways:
The UpdateContent property is not used.
For other entities this property may be used to transfer selected values from the subordinate record to the target record. When merging incidents the value of this property is ignored.
Merge is performed in the security context of the user.
Merge operations for other entities 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.
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.
Hiérarchie d'héritage
System.Object
Microsoft.Xrm.Sdk.OrganizationRequest
Microsoft.Crm.Sdk.Messages.MergeRequest
Cohérence de thread
Tous les membres statiques publics (Shared dans Visual Basic) de ce type sont thread-safe. Tous les membres d'instance ne sont pas garantis thread-safe.
Plateformes
Plateformes de développement
Windows Vista, Windows Server 2003 et
Plateformes cibles
Windows Vista,Windows XP
Change History
Voir aussi
Référence
Membres MergeRequest
Espace de noms Microsoft.Crm.Sdk.Messages
MergeResponse
Autres ressources
Merge Privileges
Sample: Merge Two Records
Customer Entities (Account, Contact)
Lead Entity Messages and Methods
How Role-Based Security Can Be Used to Control Access to Entities In CRM
How Instance-Based Security Can Be Used to Control Access to Entity Instances (Records) In CRM
Send comments about this topic to Microsoft.
© 2014 Microsoft Corporation. All rights reserved.