Bring your code 2 life

To quickly retrieve the object type codes you can add the following URL part to your CRM instance URL: /api/data/v8.2/EntityDefinitions?$select=LogicalName,ObjectTypeCode&$filter=ObjectTypeCode%20gt%209999 The output looks like this: { "@odata.context":"https://orgname.crm4.dynamics.com/api/data/v8.2/$metadata#EntityDefinitions(LogicalName,ObjectTypeCode)","value":[ { "LogicalName":"msdyn_quotebookingproduct","ObjectTypeCode":10076,"MetadataId":"eabdb23d-67d9-4c20-b72e-7358079a1afd" },{ "LogicalName":"msdyn_requirementresourcepreference","ObjectTypeCode":10017,"MetadataId":"d63ce867-9bd1-45ee-aedc-459394bedf35" },{ "LogicalName":"msdyn_rmareceiptproduct","ObjectTypeCode":10086,"MetadataId":"5b57cb66-3728-4987-8b95-ab78d5dfcf9a" },{ "LogicalName"...

Today I intended to process the email description field which contains the body of an email, but got nerved by CRM’s logic. Out of the box CRM does wrap the email body with: <pre class="mscrmpretag">YOUR CONTENT</pre> My plugin code did not expect that as I planned to parse the email’s body of certain email types as XML string (customer’s requirement). To work around this you can use this fix helper class using your own implementation of your deserialized entity class: public static class EmailXmlHandler { /// <summary> /// Gets a serialized Incident instance from a XML string. /// </summary> /// <param name="xmlString">The XML string.</param> /// <returns>Incident instance</returns> public static Incident GetIncidentFromString( string xmlString, ITracingService tracer) { XDocument xmlDoc = null ; Incident ...

Important Note: Please be reminded that the removal of the project service automation solution might be different for every new published version! This blog covered base version 1.2.0.69 of the PSA solution. In solutions, first delete the Project Service Anchor solution (if present), next the patches (highest first), lastly delete the main solution. If removal of one of the managed solutions fails you can retrieve a list of dependencies that you need to remove with the following steps: 1. First open the solution you want to remove. 2. Go to Actions menu –> select Email a Link Paste the URL into Notepad. It will look something like this: https://[YOUR_CRM_URL].crm4.dynamics.com/tools/solution/edit.aspx?id=%7b 22B859E3-395D-4560-B366-79C2CC43AB6B %7d       4.  The GUID in the URL is located between the first %7b and %7d (see the highlighted GUID above) Now that we have the GUID of the solution, we use the following ...

Currently it looks like that the Bing Maps form control cannot be rendered in the Microsoft Dynamics 365 Mobile Apps for Phone and Tablets. I added it to my form and published the changes to my Lumia 950 Windows Mobile 10 device and still missed the Bing Maps. Looks extremely like it not supported! BUT… … I found out that if you click on one of the blueish links of the Address section if will open the native Maps app of my device:

Todays I made a classical mistake. I assumed that the Bing Maps in CRM is activated by default and I was wondering why I did not see the map of my opened account record. Simple enough was the solution: Go to Settings > Administration > System Settings > Open General tab Check Yes on the “Show Bing Maps on forms” setting.