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)

(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"];
        throw new InvalidPluginExecutionException("Contacts may only be created via the CRM website.");



Popular posts from this blog

'A section using configSource may contain no other attributes or elements' error after installing Application Insights

After installing the Application Insights nuget package to an Umbraco solution, you'll get this error:

A section using 'configSource' may contain no other attributes or elements

<ExamineLuceneIndexSets configSource="config\ExamineIndex.config" />
     <log4net configSource="config\log4net.config">
             <level value="ALL" />
             <appender-ref ref="aiAppender" />
Source File: \project\web.config

This happens because part of the Application Insights installation process adds a <log4net> section to web.config.  Which would make sense, except Umbraco already has a <log4net> section in /config/log4net.config.  So as you can imagine, the solution is to manually move everything its added into that file. Unfortunately you can't just copy/paste the whole lot, but it's not particularly complicated:

Move <appender-ref ref="aiAppender" /> into the lo…

Handling double-quoted CSVs in Azure Data Factory Pipelines

Azure Data Factory by default uses a backslash as the escape character for CSVs, but we ran into an issue with this today processing one of the CSV files from  As with most CSVs they use quotes around values as normal and with double-quotes for empty values, but they also use double-quotes to escape quotes within non-empty values. This probably sounds confusing, so here's an example:

"column 1","column 2","","column 4 value is ""sort of"" like this"

The ADF pipeline failed because the double-quotes don't get escaped correctly:
ErrorCode=UserErrorSourceDataContainsMoreColumnsThanDefined, found more columns than expected column count.

The solution was to change the "Escape character" property on the dataset, by clicking the "Edit" button beneath it and manually entering "", since "" isn't in the list of escape characters.  I didn't think this would work at fir…

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…