This article describes my solution to an intermittent connection problem when using IIS Express to connect to CRM
I recently came across a problem where, despite using Business Rules to clear an attribute’s value in the past, it was not available for a specific field.
Added in a CRM 2015 Update, Business Rules can be used to clear field values by completing the following steps:
- Create new Business Rule Action:
- Select Set Field Value
- Select Field
- Set Field Type to Clear
I recently came across this problem looking at a CRM instance that had been upgraded to use early-binding. They had done something like below:
var accountInputParameters = ((Entity)context.InputParameters["Target"]).ToEntity<Account>();
This takes the InputParameters (which is of type Entity) and then bound it to the Account early-bound type.
While this seems like a good idea on the surface, as it allows all the fields of the Account to be accessed using strongly typed properties, the customer reported some strange behaviour on their Accounts.
I’ve been working in CRM Online (2016) a little for the past few weeks and I found these little bookmarklets to be helpful.
So far I have bookmarklets to
- Print the current entity’s schema name
- Print the current entity’s ID
- Reopen the current entity’s form
The Print ones are quite nice because I used CRM’s in-built notification system.