Tip #549: Cannot convert A into A

If you were playing with the uber-administrator’s way to create non-intractive users then you might have seen the following error: Cannot process argument transformation on parameter ‘conn’. Cannot convert the “Microsoft.Xrm.Tooling.Connector.CrmServiceClient” value of type “Microsoft.Xrm.Tooling.Connector.CrmServiceClient” to type “Microsoft.Xrm.Tooling.Connector.CrmServiceClient”. Ugh? Say again? Cannot convert “A” to “A”? The other possible error gives away a bit more: […]

Tip #525 Solution Export Naming Party Trick

The solution version number is often overlooked as an easy way of keeping backups of your solution separate as you configure CRM. You can number them according to a strict 4-part version numbering (e.g.,, etc.) but that’s relatively boring and tough to keep consistent. The most straight forward and easy to maintain method […]

Tip #489: Limitations of Retrieve plugins

Calculated fields is one of the best new features and is indispensable for simple calculations. Keyword here is simple. Range of functions available in calculated fields is limited (though it continues to expand from release to release). One of the “traditional” methods to add calculated field is to add a simple field and then create […]

Tip #471: What will stop your form from closing

Failed import using business rule

tl;dr Setting data validation error on the form level with Xrm.Page.ui.setFormNotification call will NOT stop form from closing, setting errors on individual controls with Xrm.Page.getControl(arg).setNotification, on the other hand, will. To achieve even better results, use business rule instead of the javascript. Slightly longer version Friend of mine pinged me to help with the script […]