SDK code

How to's - Detach an E-mail from a Queue

Abe Saldana — Thu, 12 Jun 2008 21:50:18 GMT

The E-mail to Case process one of the final steps is to make the e-mail not to display on the Queue, that is called detaching from the queue, this blog post is a follow up on one of the initial blog post on this new CrmBuzz URL, the original post was How to Detach an Email from a Queue? Summary..., so finally after some replies and follow up e-mails and questions I got the time to put in the details for one of most requested line:

returnStatus = emailDetach.EmailDetachFromQueue(EmailID, SourceQueueId);

The code snipped:

   1: public bool EmailDetachFromQueue(Guid EmailID, Guid SourceQueueID)

   2: {

   3:     bool returnvalue = false;

   4:     try

   5:     {

6:

   7:         DetachFromQueueEmailRequest detachEmail = new DetachFromQueueEmailRequest();

   8:         detachEmail.EmailId = EmailID;

   9:         detachEmail.QueueId = SourceQueueID;

10:

  11:         DetachFromQueueEmailResponse detachedEmailResponse = (DetachFromQueueEmailResponse)service.Execute(detachEmail);

12:

  13:         returnvalue = true;

14:

  15:     }

  16:     catch (System.Exception e)

  17:     {

  18:         returnvalue = false;

19:

  20:     }

21:

  22:     return returnvalue;

  23: }

The E-mail detach process will not give you too much information on the validity on the completion and you probably will need to validate making another call, so these are some of the steps for the e-mail to case (incident)

Validate E-mail content is not Spam or Duplicate
Create new Contact with E-mail address information

Create new Account with E-mail address information
Relate new Account with new Contact

Validate that E-mail is not relation to any Case (Incident)
Create new Case (Incident) with E-mail information
Detach E-mail from the Queue (Private or Public Queue)
Assign the new Case (Incident) to the User Private Queue (Incident Owner)

So these are the most common steps for converting an E-mail to a Case, I will be working on a similar process for Spam e-mails on MS Dynamics CRM 4.0 but in this version I will be using the Workflow's capabilities, stay tuned for more details on the new workflow E-mail to Case process.

Check the Articles soon you would find information related to SDK connectivity with CRM 4.0 On Premises and Online versions

Abe Saldaña

CrmBuzz.net

This all is undocumented and unsupported. Therefore you should only try these kinds of modifications if you feel comfortable working with this.
Everything here, though, is my personal opinion and is not read nor approved before being posted. No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.

How to's - Getting your Lead Status and State

Abe Saldana — Wed, 11 Jun 2008 23:07:06 GMT

Working on the previous blog post I have to get some information on the Lead's status and state, just to validate that the lead was not already qualified or disqualified and then make the conversion to an Account and to a Contact, so I started to create a SDK generic library type of assembly with the most common things I will be using on a daily basis.

Working on a lead the first thing I will be doing is check if the lead remains Open [Status = 1 and State = 0 ] or that is not Qualified [ Status = 3 and State = 1 ] and if the lead is not Disqualified [Status = 4 (Most Common - Lost) and State = 2], here is some code to get the independent values:

Getting the Lead Status Information:

   1: public int getStatus(Guid leadID)

   2: {

   3:     int returnValue;

4:

   5:     try

   6:     {

   7:         lead leadInformation = (lead)service.Retrieve(EntityName.lead.ToString(), leadID, new AllColumns());

8:

   9:         returnValue = leadInformation.statuscode.Value;

10:

  11:     }

  12:     catch( Exception)

  13:     {

  14:         returnValue = -1;

  15:     }

16:

  17:     return returnValue;

18:

  19: }

Getting the Lead State Information:

   1: public int getState(Guid leadID)

   2: {

   3:     int returnValue;

4:

   5:     try

   6:     {

   7:         lead leadInformation = (lead)service.Retrieve(EntityName.lead.ToString(), leadID, new AllColumns());

8:

   9:         returnValue = ((int)leadInformation.statecode.Value);

10:

  11:     }

  12:     catch (Exception)

  13:     {

  14:         returnValue = -1;

  15:     }

  16:     return returnValue;

  17: }

Note: the Lead State value is returned un-boxing the object value from the enum CRMSDK.LeadState

Well that is good to pull the value from the lead, but as part of the conversion process I needed to change the status from Open to Qualified, so I needed to have the Update Method and handle the validation for the update, the lead status is handle not from the Service.Update but the state is managed by the SetStateLeadRequest object, here is the code for updating the Status

   1: public bool UpdateStatus(Guid leadID, int Stateparam, int Statusparam)

   2: {

   3:     bool returnValue = false;

4:

   5:     try

   6:     {

   7:         SetStateLeadRequest leadUpdateRequest = new SetStateLeadRequest();

8:

   9:         leadUpdateRequest.EntityId = leadID ;

10:

  11:         leadUpdateRequest.LeadStatus = Statusparam;

12:

  13:         LeadState valueState = (LeadState)Enum.ToObject(typeof(LeadState),Stateparam);

  14:         leadUpdateRequest.LeadState = valueState;

15:

  16:         SetStateLeadResponse stateSet = (SetStateLeadResponse)service.Execute(leadUpdateRequest);

17:

  18:         int resultStateCode = getState(leadID);

19:

  20:         if (resultStateCode == Stateparam)

  21:         {

  22:             returnValue = true;

  23:         }

24:

  25:     }

  26:     catch(Exception)

  27:     {

  28:         returnValue = false;

  29:     }

30:

  31:     return returnValue;

32:

  33: }

After all this the conversion code was so simple to put together and easy to read, I hope the following code snipped's will work for you, keep in mind that I just put the core of the code, CRM connection objects and class definition are not included you need to create those and then test the code

Abe Saldaña

http://crmbuzz.net
Everything here, though, is my personal opinion and is not read nor approved before being posted.

No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.

Converting a Lead to Contact and Account

Abe Saldana — Wed, 28 May 2008 09:36:57 GMT

Working on a special project, I have to recreate the Lead conversion and make some other customizations on the Accounts and Contact relationship, the first code I was looking was the conversion using the Relationship mapping, I found some code regarding the related request/response, but looking under the SDK documentation finally find some code hints that I can use for the conversion.

The following is the code for converting a source entity to a target entity, taking in consideration the relationship mapping using the TargetRelatedRequest and response classes (CRM 3.0 SDK)

/// <summary>

///  Convert to Contact, Convert/Create first the Contact then the Account

/// </summary>

public Guid ConvertLead2Contact(Guid leadIdvalue)

InitializeFromRequest requestObject = new InitializeFromRequest();

requestObject.EntityMoniker = new Moniker();

requestObject.EntityMoniker.Id = leadIdvalue;

requestObject.EntityMoniker.Name = EntityName.lead.ToString();

requestObject.TargetEntityName = EntityName.contact.ToString();

requestObject.TargetFieldType = TargetFieldType.All;

InitializeFromResponse responseObject = (InitializeFromResponse)service.Execute(requestObject);

contact returnContact = (contact) responseObject.Entity;

    // You need to create the new created Contact Entity

    Guid returnContactId = service.Create(returnContact.Entity);

return returnContactId;

/// <summary>

/// Convert Lead to Account, Convert the Account after the Contact.

/// </summary>

public Guid ConvertLead2Account(Guid leadIdvalue, Guid primaryContactId)

InitializeFromRequest requestObject = new InitializeFromRequest();

      requestObject.EntityMoniker = new Moniker();

      requestObject.EntityMoniker.Id = leadIdvalue;

      requestObject.EntityMoniker.Name = EntityName.lead.ToString();

      requestObject.TargetEntityName = EntityName.account.ToString();

      requestObject.TargetFieldType = TargetFieldType.All;

InitializeFromResponse responseObject =

    (InitializeFromResponse)service.Execute(requestObject);

      account returnAccount = (account) responseObject.Entity;

if(primaryContactId != null)

    If(primaryContactId != Guid.Empty)

// relationship with the Contact

returnAccount.primarycontactid =

CrmTypes.CreateLookup(EntityName.contact.ToString(),primaryContactId);

    // You need to create the new converted Account

    Guid returnAccountId = service.Create(returnAccount.Entity);

      return returnAccountId;

Notes:

I assume you already created or added the CRM Web Service reference and created the CrmService object (service) in your project. Also I'm using the CrmTypes class to help create CRM type objects

The Lead status is not change using the TargetRelatedRequest I will post another article where is going to guide you and have code snippets to check the value, Qualify, Disqualify and Reactivate the Lead.

Hope this article will help.

Abraham Saldaña

http://crmbuzz.net

Email to Case Fetch All Records

Abe Saldana — Sun, 13 May 2007 02:17:46 GMT

I was working on my Email to Case solution and testing with copied data from production on my development CRM installation and encounter a limitation using the Fetch, the resultset was only 5000 results only but I know that I have more than that count on the queue I was testing the application....

Well I decided to create the application as a Windows NT service that will be checking every 2 minutes and process 5000 emails every time, but that will take time to process when you receive 25,000 a day, also I want the process to be optimized, in the case that we want the process to run only a few times during the day.

Looking on the SDK code I can't find any where to mentioned that 5000 records have to be returned, so I look at the registry on my development server, and found the SDK section, look for anything related to the FetchXML and found the "turnOfFetchThrottling" as 0 (zero), changed to 1 and then continue testing after that change I got all the emails coming back and the fetch took longer to return all that information.

HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM\TurnOffFetchThrottling

To process all the emails I serialized and de-serialized the resultset and process everything.

Abe Saldana

Http://www.crmbuzz.net

This all is undocumented and unsupported. Therefore you should only try these kinds of modifications if you feel comfortable with this.
Everything here, though, is my personal opinion and is not read nor approved before being posted. No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.

MS Dynamics CRM 3.0 learning and training

Abe Saldana — Tue, 08 May 2007 03:40:31 GMT

A couple of weeks ago I started working with MS CRM 3.0 for my company’s Customer Care department, this project is interesting and exiting at the same time, working on a new product and new infrastructure give me the motivation to continue learning, I will be installing and work on the configuration initially, but the plans are that I need to work on the integration for CRM and GP, taking some time before I started working on the development environment and our production staging area.

I was looking for more information on the Customization for the applications and found some link that point all the time to the same book, “Working With Microsoft Dynamics CRM 3.0” Microsoft Press, I started reading and getting to understand the application and the framework, I will start my feed on CRM and the configuration and customizations I will be making, so this is going to be more than a work on progress type a blog

Download the sample chapter on Workflow www.sonomapartners.com/microsoft-crm-book-sample.aspx

Enjoy the reading!

Abe Saldaña