Bring your code 2 life

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.

The Outlook CRM add-in includes the diagnostics tool. This allows various configuration options. For some cases it might be useful to deactivate the Outlook Synchronization. Usually, this tool is installed in this path: C:\Program Files\Microsoft Dynamics CRM\Client\res\web\bin you can open the tool from command line if you want: Microsoft.Crm.Outlook.Diagnostics.exe If you want to configure multiple machines or use policies to deactivate synchronziation you can also use a registry key for that: The key you want to look for is “ RunOutlookScheduledSync ” or “ RunOfflineScheduledSync ” if you use offline functionality. Setting to 0 (zero) disables it. Setting to 1 enables this feature. Remark: Replace ORG_ID with your actual organization id. Create Windows Registry deactivate.reg file for deactivation of sync: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\MSCRMClient\{ORG_ID}] "RunOutlookScheduledSync"=dword:...

I recently had the situation that with Dynamics 365 Online Portals not all parts are self-explaining, especially the first setup. The customer required to have multiple CRM users from multiple business units. Out-of-the-box behavior is that only the system administrator is able to create invitations in general. But what if you want to enable mulitple users to fulfill this task? I recognized that users with the system administrator role still were not able to generate the invitation code that is triggered by the worklfow below. The reason is that by default this workflow’s scope is set to “User” level. Instead it must be on “Organization” to make it fire for all portal inviters. Next step was to create a new role “Portal Inviter” which only has the permissions for the “Invitation” entity completely enabled: (whole Organization-wide with exception to the delete permission, which should be on “User”-level) So this gave me the freedom to enable certain users from ...

When you upate an exisiting solution in CRM and receive an error equal to this one: 16:33:07.66 {793dab2e-c2a4-e611-8102-c4346bad41fc} General SLA Failure 0x8004500F Cannot delete an active workflow definition. This means there is an SLA record in the system which has the status "Active". You first need to deactive that SLA record prior to importing the solution update.

When you import a CRM solution and receive this error: An error occurred while importing Convert Rules. It means you have already the same Automatic Record Creation and Update Rules deployed on the target system and they are on status "Activated". You need to deactivate those rules first prior to importing a solution or solution update.

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of ...