CRM 2011: Installer le connecteur SharePoint 2010 pour Microsoft CRM 2011
Une nouvelle fonctionnalité de Microsoft CRM 2011 est la possibilité d’utiliser SharePoint 2011 pour l’intégration des documents CRM.
Cette fonctionnalité était longuement attendue et pouvait être implémentée dans la version précédente de Microsoft CRM (4.0) en utilisant du code (voir ici et là).
CRM 2011: Finally a way to alter the ‘queue items’ view!
Yes, now it’s nearly official: you CAN alter the queue items views and set the columns you want to display!
Before:

After:

This was a long awaited need for my clients, thanks Microsoft! ![]()
CRM 2011: New ‘helpers’ for system customizers! (Part 1)
PREVIEW – Here is an overview of the new ‘helpers’ customizers have at their disposal while customizing Microsoft CRM 2011:
Deploy plugins in an IFD+OnPremise environment
If you are stuck with the Plugin Registration Tool (PRT) in an IFD environment, one test to make is this one:
- Compile the Visual Studio solution using VS 2008 or 2010
- Deploy the debug or release files PRT on the server, wherever you want, in its own folder
- On the server, launch the PluginRegistration.exe file with administrator privileges
- When you configure a CRM environment for IFD, it is recommended to configure it with IFD + OnPremise, meaning that on the server, you can access (theoretically
) the CRM by using the local address (http://localhost); therefore, if you connect to the server with a login that has access to the CRM with administrator privileges, you don’t need to enter the credentials in the PRT connection:
- This way, the PRT will use the current user’s credentials, using AD authentication, which will work; you will therefore be able to deploy your plugins by using the following addresses in the “Organization URLs” fields (you need to ensure that these URLs are the same for each OU in your CRM):

Woohoo, now I can deploy my plugins in our secured IFD environment!
How-to series: Generate auto-numbers on custom entities (part 1)
Ok, in this series, I will try to explain how to generate auto-numbers on custom entities based on the user’s preferences (length of the auto-number, prefix, suffix, increment value, etc.)
Tip: Use that default ‘name’ field in custom entities!
Sometimes it is useful, sometimes it is not…when you create a new custom entity in Microsoft CRM, there is always one default field called ‘name’ which is a varchar field.
One will say that you can always make it ‘non-mandatory’ and remove it from the form, but the problem lies in the search view, where you will not be able to remove it!
How-to series: Easily debug your CRM JavaScript code in IE8
Well, as a lot of you may know it, you can put your own JavaScript code in the forms or fields events (OnChange, OnLoad & OnSave events).
Set a datetime field to current date
Of course you can find it using Google or Bing, but for the sake of it, here is the code you need to use in the form’s OnLoad() event to set the default value to the current date in a datetime field on Microsoft CRM :
var CRMFORMTYPE_CREATE = 1; var CRMFORMTYPE_UPDATE = 2; var CRMFORMTYPE_READONLY = 3; var CRMFORMTYPE_DISABLED = 4; var CRMFORMTYPE_BULKEDIT = 6; switch (crmForm.FormType) { case CRMFORMTYPE_CREATE: crmForm.all.YOURFIELD.DataValue = new Date(); break; case CRMFORMTYPE_UPDATE: case CRMFORMTYPE_READONLY: case CRMFORMTYPE_DISABLED: case CRMFORMTYPE_BULKEDIT: break; }
Calculate the remaining characters on the description field
Warning: this type of customization is not supported by Microsoft therefore use it at your own risks!
My client asked me if it was possible to get a “counter” on how many characters you could enter when updating the description field on an activity such as a task, a phone call, and so on.
The curious case of the case entity
I believe most people know about this: in the case entity, there are 2 attributes that can be used to map a case to either an account and/or a contact.
These 2 attributes are:
- customerid
- responsiblecontactid

What if your client’s business requirements tell you to put both information on the case form? Let me explain: my client wants to be able to track from which contact the incident originated and for which account, resulting in a double way on how to find the incident.
You might say “All right dude, this is easy! Let’s put both the attributes on the form and it will solve the problem right away”. Yes it can, alas for my client it will not! “But why?” will you ask me, it looks like you can designate both the contact and the account on the case, so it’s OK. But no. “Why not?”
Well, if you designate a responsible contact on a case, the case will not be linked to the contact in the contact form detail!


