This statement holds true whether you are updating attributes through the SDK dlls or over web services. It doesn’t matter whether you’re coding for a plugin, workflow assembly, Silverlight app or some external custom application like a windows application or web application. The potential outcome in all the scenarios will be the same! What’s the outcome? Triggering other automation unwantedly!
This caused me some headaches today, so to save you the cost of a box of paracetamols i thought I’d shout it out! If you ever find yourself writing code to perform your own mail merges based on CRM mail merge tags watch out for how CRM shortens mail merge tags when involving related entities. What do I mean by this? Well let’s say we create a mail merge that is based on case. In this merge we include the primary contacts name and address. In doing this we basically add a related field in to our mail merge.
If you use virtual machines to host MSCRM and find yourself having to develop plugins or workflow assemblies inside your virtual machine then this is for you! Tired of speed issues huh? I don’t blame you! Its not nice when the Visual Studio inside your image can’t keep up with the speed of your actions. Anyway, why are you coding inside your image!? Oh… to debug? Well install the remote debugger on to the virtual machine, develop on your local machine, deploy your assemblies to the virtual machine, and to debug attach to the process you require which is exposed by the remote debugger.
While writing assemblies for MSCRM 2011 the chances are at some point you will want to get a record count. Its a typical check right? Perform a search on a set criteria, retrieve the record count from your search and decide what to do on the outcome of the count. Well when coding the LINQ statement to achieve this you might of noticed the Count method. However using that method will give you the following error message “The method ‘Count’ is not supported”. Strange, well I decided to check the SDK for the best way to get a count… Nothing… I decided to check the programming samples for latebinding through LINQ… Nothing…
This is one that a lot of people have asked me about over the past few months. I thought I’d throw it out there and warn other people. We don’t want you spending ages trying to connect your Silverlight applications to MSCRM, trying to work out why they are not authenticating and performing their queries correctly. Only to kick yourself when you work out what the problem is! So whats the problem? Simple, Silverlight can’t connect to MSCRM, Whats the solution? Simple, check your bindings in Deployment Manager!