Unsupported

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.

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 Templates tag merging

Abe Saldana — Fri, 27 Jul 2007 02:31:31 GMT

I was working on a small project making some changes to the Email Templates when I got the requirements to create some meta tags and implement detail logic that will depend on the value of a field, that was interesting and challenging at the same time and make that customization been supported by the infrastructure of CRM, well I made changes but these are unsupported code, these are the steps on how to make the customizations:

1) Make the modifications to ...\Activities\email\edit.aspx file.

2) Update the javascript function ApplyTemplate() and include the functionality required for the customer.

function ApplyTemplate()

{ var oTarget = ChooseTemplateTarget();

if (oTarget == null)

return;

var sUrl = "/_grid/cmds/dlg_bulkemail.aspx?bulkemail=false" + "&objectTypeCode=" + oTarget.otype + "&objectId=" + oTarget.oid;

var sResponse = openStdDlg(sUrl, null, 550, 850);

if (sResponse != null)

{

// Get Response from the email template

var templatedescription = sResponse.EmailBody ;

// Get the contact/account id for searching

var ToRecipients = crmForm.all.to.Items();

var customerid = ToRecipients[0].id

// Get status for the contact/account

var validationonBoolean = GetWebServiceValidation(customerid);

if (validationonBoolean)

{

// Customer Validation is TRUE

templatedescription = stringReplace(templatedescription,"[LOCALEDMESSAGE]","Replace message with English version");

}else

{

// Customer Validation is FALSE

templatedescription = stringReplace(templatedescription,"[LOCALEDMESSAGE]","Replace message with Spanish version");

}

crmForm.all.description.InsertValue ( templatedescription );

}

3) After that I used the normal string.Replace function finding the function only replaced the first instance, that will take me to the second correction and make the following function:

function stringReplace(originalString, findText, replaceText)

{

var pos = 0;

var len = findText.length;

pos = originalString.indexOf(findText);

while (pos != -1)

{

preString = originalString.substring(0,pos);

postString = originalString.substring(pos + len,

originalString.length);

originalString = preString + replaceText + postString;

pos = originalString.indexOf(findText);

}

return originalString;

}

The rest was a simple implementation of your Web Services call, please read the previous blog called "How to call my web service using Javascript?"

Remember that this is an Unsupported customization and when a service patch come it will provably remove those customizations.

I hope this information help you to add more flexibility to the email templates.

Abe Saldaña

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.