Deprecation of unsupported configurations in CRM Online 2015 Update

Important information regarding the next release of Microsoft Dynamics CRM 2015

As with previous CRM releases, Microsoft have added new features and removed other items from their supported configurations list to keep current with technology and allow the best product possible.

This article lists the items no longer supported in the latest version of Microsoft Dynamics CRM 2015.

If you have any questions relating to the below or customisations you are unsure about, QGate can help.  You can use our Contact Us page to find out more.

Changes in browser support

For the next release, Microsoft are discontinuing support for the following browser versions:

• Internet Explorer 8
• Internet Explorer 9

Please see supported versions of Internet Explorer.

Note: Accessing CRM 2015 Update via IE8 or IE9 will not block or redirect you to a different experience. Code fixes will only be considered for issues that can be reproduced with a supported Microsoft browser.

Additional information on document modes is available from MSDN

Changes in items specific to the CRM application

Microsoft are removing the support of the following client SDK (JavaScript) APIs:

• context.getServerUrl (use getClientUrl instead)
• context.isOutLookClient (use client.getClient instead)
• context.isOutlookOnline (use client.getClientStateinstead)

Please see Client-side Context Reference for CRM 2013 for alternative methods to use.

This means that if your customisations are using any of these API commands, your code will likely break after you update to CRM Online 2015 Update. In addition, Microsoft will be proactively identifying customers that are affected by this change and will be sending targeted communication. To see more, please visit the What’s changing in the next release, which summarises all the SDK related changes.

Microsoft are modifying the possible return values from Xrm.Page.ui.getFormType to remove the Read Optimised and CRM 4.0 Quick Form types. This means that they are removing two values from the possible results of getFormType. However, it’s unlikely that your code will be affected by this because the forms types were removed in CRM 2013 SP1 and CRM Online Spring ‘14.

Form System

Microsoft are removing the support of the following form item

• CRM 2011 or Information forms that Microsoft updated in CRM 2013 for certain updated entities.

This means that you should migrate your forms for just these entities to use the new CRM 2013 SP1 and CRM Online Spring ’14 form system before upgrading to CRM Online 2015 Update. If you are unable to do this, these forms will still work in CRM Online 2015 Update; however, new functionality that Microsoft make available in CRM Online 2015 Update may not be available on these forms. Microsoft strongly encourage you to migrate to the new Form System.

For more information about how to migrate your forms, please see the following article Update your forms to Microsoft Dynamics CRM 2013 or Microsoft Dynamics CRM Online Fall ’13.

Entities

The Kit type of Product will be deprecated, which means that Microsoft will do base testing only and will be removing this feature in a future release. Please update any customisations that use products defined as kits’failing to do so will block and conflict with new product type advancements in the near future. To learn more about Kit type see Product catalog entities.

Email Router

Support for Exchange 2007 connectivity to and from the Microsoft Dynamics CRM Email Router will be deprecated, which means that Microsoft will do base testing only and will be removing this capability from the Email Router in a future release. Please see email router supported versions of Exchange Server.

2007 SDK SOAP Endpoint

Microsoft will be removing this endpoint in CRM Online 2015 Update, which was deprecated in CRM 2013 SP1 and CRM Online Spring ‘14. You shouldn’t use this endpoint for any new extensions.

Office 365 Security Role Changes

Microsoft have updated the way that CRM Online synchronises data with Office 365. There will be a slight change to how security groups can be chosen to associate to an organisation instance. Previously, it was possible in the instance settings page to choose either a Security Group or a Security Role (such as Company Administrator) and have only licensed, enabled users that belonged to that Security Group or Role enabled in the corresponding CRM organisation. After the upcoming changes, it will not be possible to choose a Security Role for an organisation instance in the instance settings page in the Office 365 Admin Centre.

This change impacts only the user experience of selecting a Security Group for user sync management; it does not impact the synchronisation process for those organisations that have already selected a Security Role. In those cases, users will still be enabled or disabled in the organisation instance based on membership in the selected Security Role.

However, going forward you will need to decide on a new Security Group to replace the existing Security Role for user membership management.

In addition, Microsoft will be proactively identifying customers that are affected by this change and will be sending a targeted communication.

Want to learn about the new Microsoft Dynamics CRM Online 2015 Update release?

You can learn more about the new Microsoft Dynamics CRM Online 2015 Update by visiting the Get ready for the next release page or by visiting the QGate Knowledgebase Microsoft Dynamics CRM Product Update – Frequently Asked Questions.