Microsoft Dynamics CRM 2015 and Google Chrome 39 Compatibility

Microsoft introduced cross-browser support for Microsoft Dynamics CRM way back with Update Rollup 12 for Microsoft Dynamics CRM 2011, including support for Google Chrome. However, we at xRM ( and others have discovered compatibility issues with Google Chrome that persist in Microsoft Dynamics CRM 2015.

Presently, Dynamics CRM 2015 is supported on the following browsers:

  • Internet Explorer
  • Google Chrome
  • Firefox
  • Safari

For more details about other supported browsers and operating systems, please see Microsoft Dynamics CRM 2015 System Requirements.

When Google Chrome reached version 37 back in September 2014, many CRM users reported issues such as an inability to export data to Excel, system settings not being saved, the Form Editor not accepting changes, and errors when modifying Status Reason fields.

The root cause of these issues is that Google deprecated the showModalDialog API in Chrome. Basically, showModalDialog allows applications to show a dialog of HTML content while simultaneously freezing all other content. By default, showModalDialog is turned off in Chrome. However, Google has added a “temporary Enterprise Policy setting to re-enable showModalDialog. In May 2015 this setting will be removed and showModalDialog will be completely removed from Chromium,” per the Chromium Blog. (Chromium is the open source browser upon which Google Chrome and some other browsers are built.)

The following explanation is found on


Enable deprecated web platform features for a limited time

Data type:

List of strings

Windows registry location:


Mac/Linux preference name:


Supported on:

  • Chromium (Linux, Mac, Windows) since version 37
  • Chromium OS (Chromium OS) since version 37
  • Chromium (Android) since version 37

Supported features:

Dynamic Policy Refresh: Yes, Per Profile: Yes


Specify a list of deprecated web platform features to re-enable temporarily. This policy gives administrators the ability to re-enable deprecated web platform features for a limited time. Features are identified by a string tag and the features corresponding to the tags included in the list specified by this policy will get re-enabled. If this policy is left not set, or the list is empty or does not match one of the supported string tags, all deprecated web platform features will remain disabled. While the policy itself is supported on the above platforms, the feature it is enabling may be available on fewer platforms. Not all deprecated Web Platform features can be re-enabled. Only the ones explicitly listed below can be for a limited period of time, which is different per feature. The general format of the string tag will be [DeprecatedFeatureName]_EffectiveUntil[yyyymmdd]. As reference, you can find the intent behind the Web Platform feature changes at

  • “ShowModalDialog_EffectiveUntil20150430” = Enable ShowModalDialog API through 2015.04.30

Example value:


Software\Policies\Chromium\EnableDeprecatedWebPlatformFeatures\1 = “ShowModalDialog_EffectiveUntil20150430”







Microsoft Support provides its own instructions on how to resolve the issue:

  1. Download ADM Policy Templates for Windows
  2. Extract the downloaded files, then navigate to Start | Run: gpedit.msc
  3. Navigate to Local Computer Policy | Computer Configuration | Administrative Templates
  4. Right-click Administrative Templates and select Add/Remove Templates
  5. Add the downloaded chrome.adm templates of Windows via the dialog for the specific language
  6. Once the template is added, a Google Chrome folder will appear under ‘Classic Administrative Templates’
  7. Select EnableDeprecatedWebPlatformFeatures setting in the right column. Right-click the setting and select Edit
  8. Edit the EnableDeprecatedWebPlatformFeatures as shown below:
    1. Paste in the following string value: ShowModalDialog_EffectiveUntil20150430
    2. Click OK on the Show Contents dialog
    3. Click Apply and OK on the Enabled Deprecated Webplatform Features dialog
  9. Restart the Google Chrome browser and type chrome://policy in the address bar
    1. You should observe that this deprecated feature is now enabled.

It is important to emphasize that this temporary solution will only be available until May 2015. At that time, showModalDialog will be completely removed from Chromium (and therefore from Google Chrome which is based on Chromium). Presently, it is not clear how Microsoft Dynamics CRM will function when running in Chrome after that happens.

Another issue is that Google Chrome does not allow the rollback to an older version of the browser.

To avoid these issues altogether, users can sign into Microsoft Dynamics CRM in either Internet Explorer or Firefox. On a side note, Firefox does keep a public archive or their builds available. If Firefox ever releases a version that is not compatible with Microsoft Dynamics CRM, you will be able to roll back to the previous version that does work.

Technically, Microsoft Dynamics CRM supports browser compatibility for Internet Explorer, Safari, Firefox, and even Chrome (assuming you make the registry changes). But it’s unclear at this time how that will change in May 2015, if it even does change. Be sure to plan ahead and stay tuned.

Meanwhile, xRM recommends that customers avoid Google Chrome 39 with Microsoft Dynamics CRM 2015.

If you would like to learn more tips, tricks, and tutorials such as this one, please check out our xRM blog and our Success Portal. If you would like to receive training from our team of experts, please inquire about our QuickStart Training.

Read More

Troubleshooting Data Import Errors

Microsoft Dynamics CRM provides some useful tools for importing your data, such as templates, the Import Data Wizard, and data maps. These features are designed to make the import process as pain free as possible. However, we at xRM ( know that complications and errors can still arise, and it can be frustrating if you aren’t able to locate the source of the problem. In this post, let’s examine two of these common errors, how we find them, and how we resolve them.

First, let’s take a look at the data that we want to import. It’s in a .csv file we created in Excel:

Troubleshooting Data Import Errors

This is a simple list of Contact records we want to bring into our CRM database. It has just five attributes: First Name, Last Name, Title, Business, and Business Phone. Let’s proceed with the import and see what happens. One way of doing this data is by navigating to Settings > Data Management, and then clicking Imports. Next, click the Import Data button in the command bar and proceed through the Import Data Wizard that appears.

Troubleshooting Data Import Errors

Now, it is time to map the fields. As you can see above, I’ve mapped the “Business” column to the Company Name field of the related Account record. Let’s finish the import and then examine the results.

Troubleshooting Data Import Errors

Why did we have five errors and zero successes? Rather than trying to import the same document again as is and running into the same problem, let’s first locate the issue. To do this, we can open the record of the import itself. In this example, we can click “Client List.csv.” When the record window opens, click the Failures label in the Related pane on the left of the form.

Troubleshooting Data Import Errors

In the Import Log, we can see a description of why each record was unsuccessfully imported. The first four records could not be brought in because a lookup reference could not be resolved. This is a common mistake new users to Dynamics CRM encounter when bringing in new contact records: trying to import new records from two different entities in a single file.

The Excel document shown above represents both Accounts and Contacts. The “Business” column references the Account records. If those records do not already exist when bringing in the related Contact records, the lookup reference error occurs. To avoid this error, we can copy and paste the Business column into another Excel file, along with any other data relevant to the Account records. We then import the Accounts before we import the Contacts. This time, the lookup reference error won’t trigger because there will be existing Account records with which the Contacts can be related.

What about the duplicate error for the last record? In the ImportLog Associated View there is a column called “Original Row Number.” This helps us locate the exact record in the spreadsheet that is causing the error. In this example, it’s row 6, “Becky Miller.” Let’s say we know for a fact that Becky does not already exist in our database. So how could a duplicate have been detected? To find the answer, let’s navigate to Settings > Data Management > Duplicate Detection Rules.

In a nutshell, a Duplicate Detection Rule in Dynamics CRM helps maintain the integrity of our data. When records are imported or created, the system will use any published rule to verify that the incoming record does not already exist. An example of such a rule is “Contacts with the same first and last name.” By default, Dynamics CRM comes with nine published Duplicate Detection Rules. Any of them can be deactivated and new ones can be created. Let’s take a look at the published rules for Contact records.

Troubleshooting Data Import Errors

We know Becky does not have the same first and last name as anyone in our system. We also know that we’re not importing email addresses in this import, so that rule couldn’t have triggered the error. So that leaves “Contacts with the same business phone number” as the only rule preventing the successful import of Becky’s record. This is actually a common misstep in imports. What happens is users attempt to import a group of contact records that work for the same company. Oftentimes, the business phone number will be the same for all of the contacts because it is the company phone number, not a direct line. This triggers the Duplicate Detection Rule and prevents all but one of the Contact records from being created. Becky already has a coworker in the system with the same business phone listing. Therefore, the system sees this as a duplicate record.

To prevent this from happening, we can simply select the rule, and then click the Unpublish button. We’ll then be able to import Becky’s record successfully. We can even Publish the rule again once the import is complete.

The lookup reference and duplicate detection errors are common in data imports, but they certainly aren’t the only problems that can occur. Be sure to check the record of import in CRM, especially the listed failures to locate the source of the problem and hopefully find a solution with as little headache as possible.

If you would like to learn more tips, tricks, and tutorials such as this one, please check out our xRM blog and our Success Portal. If you would like to receive training from our team of experts, please inquire about our QuickStart Training.

Read More

Changes Coming to Microsoft Dynamics CRM Online 2015

If you are a current Microsoft Dynamics CRM Online subscriber, you have undoubtedly noticed the Update scheduled message appearing immediately under the navigation bar when you log into Microsoft Dynamics CRM Online. While the update is optional, Microsoft Dynamics CRM Online 2015 is a worthwhile upgrade that adds several welcome features, including global search, improved Products, and more powerful Business Process Flows.

Changes Coming to Microsoft Dynamics CRM Online 2015

However, Microsoft Dynamics CRM Online 2015 also removes support for old versions of Internet Explorer, several client SDK APIs, and a few other deprecated features. You should make sure that any customizations you have deployed to your CRM organization don’t depend on these features before you complete the update. You will also want to make sure that compatible web browser versions are in place before you update. You can reschedule your update to Microsoft Dynamics CRM Online 2015 to give your organization time to update any custom applications and upgrade any user workstations.

Changes in browser support for Microsoft Dynamics CRM 2015

One obvious change is that Microsoft is removing support for Internet Explorer 8 and Internet Explorer 9 from Microsoft Dynamics CRM Online 2015. You will need to make sure that all user workstations have IE 10, IE 11, or the most recent version of Mozilla Firefox before you update to CRM Online 2015. Please note that even though Google Chrome is listed as a compatible browser, we still do not recommend it due to compatibility issues.

API Changes in Microsoft Dynamics CRM Online 2015

Microsoft has also removed support for several JavaScript APIs, and if you use any of these APIs in your code, your code will likely break once you update to CRM Online 2015. The deprecated APIs are as follows:

  • · context.getServerURL (Microsoft recommends using getClientURL instead.)
  • · context.isOutlookClient (Microsoft recommends using client.getClient instead.)
  • · context.isOutlookOnline (Microsoft recommends using client.get instead.)

Other Deprecated Features in Microsoft Dynamics CRM Online 2015

  • · Support for the Kit type of Product has been removed.
  • · Microsoft Dynamics CRM Email Router support for Exchange 2007 has been removed.
  • · Support for the 2007 SDK SOAP Endpoint has been removed.

You can learn more about the changes coming to Microsoft Dynamics CRM Online 2015 by visiting the Get ready for the next release page.

Are Your Ready for Microsoft Dynamics CRM 2015

If you are unsure if your custom code is ready for Microsoft Dynamics CRM, xRM can help. Our expert CRM consultants can examine your custom code and determine what steps need to be taken to ensure your code’s readiness for CRM 2015. Schedule your complimentary Microsoft Dynamics CRM Online 2015 Code Readiness Analysis today.

Changes Coming to Microsoft Dynamics CRM Online 2015

Read More