Skip to main content

Preventing the Dynamics CRM Outlook add-in from creating contacts, forever

It's an ongoing issue here wherein a misconfigured / misbehaving Outlook client sometimes creates duplicate or redundant contacts in our CRM, and I've seen many blog posts and forum threads discussing the various ways of getting around it.  Unfortunately they all require user-specific configuration, whereas I wanted to banish the problem across the board once-and-for-all.  Completely by accident I came across a solution, which in retrospect is extremely obvious and I'm rather embarrassed that I didn't figure it out sooner!

It all hinges on the fact that the Dynamics CRM website will execute javascript on the form, and of course the Outlook add-in will not, as no form is loaded (although there is a way to get one, which is covered here too).

Add a boolean field to your contact entity called "Permit Creation", which defaults to no.
Add it to the contact form, but mark it as hidden.
Add the following javascript to the contact form in the page load event:

if(!Xrm.Page.context.isOutlookClient() && Xrm.Page.ui.getFormType() == 1)
{
Xrm.Page.getAttribute["new_permitcreation"].setValue(true);
}

(The isOutlookClient() / getFormType() check isn't really needed for this, but prevents people from accidentally creating contacts via forms in Outlook too, if that's what you want)

Next, create a CRM plugin using Visual Studio that does the following:
(obviously this is not the complete plugin code, just the part that matters)

bool permitted = (bool)entity.Attributes["new_permitcreation"];
if(!permitted)
{
        throw new InvalidPluginExecutionException("Contacts may only be created via the CRM website.");
}

Easy!

Comments

Popular posts from this blog

Using WiX to create an event source during install of a .NET framework project

Edit: so I guess I wasn't the only one confused with this stuff, as it's been my most popular post by far!  If I've helped you out or saved you some time, please let me know in the comments :)

In order for this to work, you have to add references to WixUtilExtension and WixNetFxExtension to your WiX project.  Once that's done, add this inside a <Component> element:

<Util:EventSourcexmlns:Util="http://schemas.microsoft.com/wix/UtilExtension"Name="EVENTSOURCEGOESHERE"Log="Application"EventMessageFile="[NETFRAMEWORK40FULLINSTALLROOTDIR]EventLogMessages.dll" />
Obviously replace EVENTSOURCEGOESHERE with your event source name.  NETFRAMEWORK40FULLINSTALLROOTDIR is a property set by the WixNetFxExtension which stores the path to the .NET framework v4 directory, but you can replace this with the corresponding property for the directory containing the relevant EventLogMessages.dll file.  So if you're using the .NET framewo…

How to make yourself a Dynamics CRM 2011 Deployment Administrator

Today I needed to deactivate one of our Dynamics organisations, but when I opened the Dynamics Deployment Manager, I received the following error:

"Only the Deployment Administrators are able to use Deployment Manager. You are not a Deployment Administrator."
Bummer. I did a bit of Googling and found this post by Ronald Lemmen (thanks for pointing me in the right direction!).  Since the Dynamics Deployment Manager is obviously checking the MSCRM_CONFIG database for this information I attached a database trace to it and found that it's executing these queries (among many others):

exec sp_executesql N'SELECT  Id, [DefaultOrganizationId], [IsDisabled], [Name]   FROM [SystemUser]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar(41)',@Name0=N'{My windows domain account}'
exec sp_executesql N'SELECT  Id, [Name], [UniqueifierId]   FROM [SecurityRole]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar…

Umbraco Deployment Checklist

This is primarily aimed at deploying from Visual Studio to an Azure Web App + Azure SQL database, feel free to skip bits that aren't relevant if you're doing other things.

Prerequisites for developing locally:
Visual Studio (obviously)
Ensure IIS URL Rewrite module is installed using web platform installer (other downloads from MS documentation don't seem to work)

Set up Azure:
Make a new SQL Database in Azure, take note of the server name, database name, admin login and admin password.  If you already have a server and resource group, automate with Powershell as shown below (you'll need to replace the param values):
New-AzureRmSqlDatabase -DatabaseName "UmbracoDatabase" -ServerName "TheServer" -ResourceGroupName "Whatever" -Edition "Basic"
Add your IP to the Azure SQL db firewall so Umbraco can connect to it later when running locally
Create a new Azure web app, either manually or via Powershell:
New-AzureRmWebApp -ResourceGroupName…