RemoveItemCampaignRequest-klasse
Contains the data that is needed to remove an item from a campaign.
Navneområde: Microsoft.Crm.Sdk.Messages
Assembly: Microsoft.Crm.Sdk.Proxy (i Microsoft.Crm.Sdk.Proxy.dll)
Syntaks
'Deklaration
<DataContractAttribute(Namespace:="https://schemas.microsoft.com/crm/2011/Contracts")> _
Public NotInheritable Class RemoveItemCampaignRequest
Inherits OrganizationRequest
[DataContractAttribute(Namespace="https://schemas.microsoft.com/crm/2011/Contracts")]
public sealed class RemoveItemCampaignRequest : OrganizationRequest
Bemærkninger
Message Availability
Denne meddelelse fungerer, uanset om den kaldende har forbindelse til serveren eller arbejder offline.
Usage
Pass an instance of this class to the Execute method, which returns an instance of RemoveItemCampaignResponse.
Privileges and Access Rights
To perform this action, the caller must have privileges on the Campaign entity and access rights on the records specified in the CampaignId property and the EntityId property.
For a complete list of the required privileges, see RemoveItemCampaign Privileges.
Nedarvningshierarki
System.Object
Microsoft.Xrm.Sdk.OrganizationRequest
Microsoft.Crm.Sdk.Messages.RemoveItemCampaignRequest
Sikkerhed i tråd
Alle offentlige statiske (Shared i Visual Basic) medlemmer af denne type er trådsikret. Alle medlemmer af forekomsten er ikke garanteret trådsikkerhed.
Platforme
Development Platforms
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.
Target Platforms
Windows Server 2008,Windows Server 2012,Windows 7
Se også
Reference
RemoveItemCampaignRequest-medlemmer
Microsoft.Crm.Sdk.Messages-navneområde
RemoveItemCampaignResponse
Andre ressourcer
RemoveItemCampaign Privileges
CampaignItem Intersect Entity Metadata
Marketing Entities (Campaign, List)
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.
© 2015 Microsoft. All rights reserved.