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.

Purging rows on Princiapl Object Access

Abe Saldana — Tue, 08 May 2007 03:23:24 GMT

[Disclaimer:All postings are provided "AS IS" with no warranties, and confer no rights.]

Purging some tables on Crm is simple as calling the delete service and make sure that everything continues running properly, but when you have more than 10 million rows on one table (PrincipalObjectAccess) how do you will be able to take the delete process on stages?

[MS Crm support response: There is an un-supported option that you could try if you want to get rid of all sharing that is currently setup in CRM. You could directly update the PrincipalObjectAccess table and set the AccessRightsMask and InheritedAccessRightsMask columns to 0. Then we have a deletion service that will go through and automatically clean up that table. This is not technically supported, but if you want to remove all sharing this could be an option that you could do.

Ok that is awesome, but how to identify the rows that are not in use or ready to be deleted.

This is one of the Sql scripts to get the total of rows ready to be deleted and terminated

declare @totalRows int
declare @ToDelete int
declare @ToDeleteMarked int

SELECT @totalRows = count( * )
FROM PrincipalObjectAccess (nolock)

SELECT @ToDelete= count( *)
FROM PrincipalObjectAccess (nolock)
where AccessRightsMask = 0
and InheritedAccessRightsMask > 0

SELECT @ToDeleteMarked= count( *)
FROM PrincipalObjectAccess (nolock)
where AccessRightsMask = 0
and InheritedAccessRightsMask = 0

Select @totalRows as TotalRows,
@ToDelete as ToDelete,
(@totalRows - @ToDelete) as RemainingRows,
@ToDeleteMarked as ToDeleteMarked

Using the previous script will give you the totals only the following script is the one that will update your columns and marked the rows for deletion..

[IMPORTANT: Make sure that you have SQL database backups before trying this and know that you may have to restore your databases if you run into issues. Also this can ONLY be done if you want to remove ALL sharing. There is not a way to leave some sharing intact. ]

SELECT top 500000 *
into #TempPOA FROM
PrincipalObjectAccess (nolock)
where AccessRightsMask = 0
and InheritedAccessRightsMask > 0

update PrincipalObjectAccess
set InheritedAccessRightsMask = 0
where rowguid in (Select rowguid from #tempPOA)

drop table #TempPOA

After finishing marking all the rows for deletion, now you can run the delete service, stop the service (not required) then run the following dos command

C:\Program Files\Microsoft CRM\Server\bin\CrmDeletionService.exe -runonce

[NOTE: -runonce = Clean up database right now.]

we schedule the deletion service to run only once a day, on a business downtime, this process will keep your tables purged and on optimal conditions

regards,
Abe Saldaña

Performance

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

Purging rows on Princiapl Object Access