QualifyLeadRequest-klasse
Contains the data that is needed to qualify a lead and create account, contact, and opportunity records that are linked to the originating lead record.
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 QualifyLeadRequest
Inherits OrganizationRequest
[DataContractAttribute(Namespace="https://schemas.microsoft.com/crm/2011/Contracts")]
public sealed class QualifyLeadRequest : OrganizationRequest
Eksempel
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.
// Qualify the first lead, creating an account and a contact from it, but
// not creating an opportunity.
var qualifyIntoAccountContactReq = new QualifyLeadRequest
{
CreateAccount = true,
CreateContact = true,
LeadId = new EntityReference(Lead.EntityLogicalName, _lead1Id),
Status = new OptionSetValue((int)lead_statuscode.Qualified)
};
var qualifyIntoAccountContactRes =
(QualifyLeadResponse)_serviceProxy.Execute(qualifyIntoAccountContactReq);
Console.WriteLine(" The first lead was qualified.");
Bemærkninger
Message Availability
Denne meddelelse fungerer, uanset om den kaldende har forbindelse til serveren eller arbejder offline.
Usage
Overfør en forekomst af denne klasse til Execute method, which returns an instance of the QualifyLeadResponse class.
Privileges and Access Rights
To perform this action, the caller must have privileges on the Lead, Account, Contact, Opportunity, TransactionCurrency, and Campaign entities. The caller must also have access rights on the specified records in the following properties: LeadId, OpportunityCurrencyId, OpportunityCustomerId, and SourceCampaignId. For a complete list of required privileges, see QualifyLead Privileges.
Notes for Callers
If SharePoint integration is enabled, the document location records for the lead are copied for the newly created account, contact, and opportunity.
If you set the CreateAccount property and the CreateContact property to true, the created account becomes a parent (Contact.Parentcustomerid) of the contact and the contact becomes a primary contact (Account.PrimaryContactId) for the account.
Nedarvningshierarki
System.Object
Microsoft.Xrm.Sdk.OrganizationRequest
Microsoft.Crm.Sdk.Messages.QualifyLeadRequest
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
Change History
Se også
Reference
QualifyLeadRequest-medlemmer
Microsoft.Crm.Sdk.Messages-navneområde
QualifyLeadResponse
Andre ressourcer
Sales Entities (Lead, Opportunity, Competitor, Quote, Order, Invoice)
Sample: Qualify a Lead
Customer Entities (Account, Contact)
TransactionCurrency (Currency) Entity
Campaign Entities
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
QualifyLead Privileges
Send comments about this topic to Microsoft.
© 2015 Microsoft. All rights reserved.