With the SetStateRequest message now being deprecated you may find yourself starting to amend any code to use an Update request instead. Please note though that any plugins steps registered on SetStateRequest will not subsequently trigger on updat...
Until the release of 2016 Update 1 there was no easy way of managing users’ signatures. Instead we’d make use of email templates, which was less than ideal. Thankfully Microsoft rectified this and introduced a new email signature fea...
Sounds bonkers but it’s true. Whilst making some amendments to a custom product picker (HTML web resource) I added a reference to ClientGlobalContext.js.aspx to avoid relying on getting the context from the parent window, which I had some i...
Despite being a CRM developer for almost three years now I still find myself having, on occasions, to refer to the Microsoft Developer Network for common Xrm.Page functions when writing client-side script, usually forgetting whether functions are ...
Back when I worked for a CRM partner, and in my early days of CRM development, I would often get asked how long something would take to code – a “ballpark figure” – usually for a small requirement or change request. Invar...
In a previous post I discussed some of the issues and limitations when using the Customer field type. One of the issues I highlighted was that when viewing Recent Cases on the Contact it would only return Cases where the Contact was set as the Cu...
When writing JavaScript for CRM forms I like to encase all form functions within a namespace library in a very similar fashion to what Microsoft suggest here. It ends up looking like follows.
//If the LSD namespace object isn’t defined, create it...
Since upgrading to Dynamics CRM 2016 I have made great use of only adding the entity components required to solutions rather than the entire entity itself. The key reason why you would want to do this is to ensure that no unintended changes are m...