As we ship the Microsoft Dynamics CRM 2013 Service Pack 1 and CRM Online Spring ‘14 releases, we’re looking ahead to our next release of CRM. As with other releases of CRM in the past, we find the need to add and remove items from our supported configurations list to keep current with technology, and allow us to provide you the best product possible.
For the next release, we’re removing the following operating systems from our Microsoft Dynamics CRM Server support matrix:
We’re removing the following SQL Server versions from our Microsoft Dynamics CRM Server support matrix:
We’re removing Microsoft Dynamics CRM for Outlook support for:
Our current plan for Microsoft Dynamics CRM Server is to target only Windows Server 2012, Windows Server 2012 R2, and SQL Server 2012 for the next release time frame.
Note that we’re exploring support for SQL Server 2014 with Microsoft Dynamics CRM Server, but we haven’t made a decision at this time.
This means that if your customizations are using any of these API commands, your code will likely break after you upgrade CRM.
We’re modifying the possible return values from Xrm.Page.ui.getFormType to remove the Read Optimized and CRM 4.0 QuickForm Types. This means that we’re removing two values from the possible results of getFormType. However, it’s unlikely that your code will be affected by this because we removed the forms types in CRM 2013.
Please see Client-side Context Reference for CRM 2013 for alternative methods to use
We’re removing the following form items:
This means that you must upgrade your forms to use the new CRM 2013 form system before upgrading to the next release.
The Kit type of Product will be deprecated, which means that we’ll do base testing only and will be removing this feature in a future release. Please update your customizations to not use this entity.
We’re making database merge mandatory on upgrade. This means that you won’t be able to bypass this process during the upgrade from CRM 2013 to the next release of CRM.
Support for Exchange 2007 connectivity to and from the CRM Email Router will be deprecated, which means that we’ll do base testing only and will be removing this capability from the CRM Email Router in a future release.
We’re dropping support for Internet Explorer 8 and Internet Explorer 9.
Note that Internet Explorer 8 and 9 won’t route to Microsoft Dynamics CRM for phones by default, they will continue to route to the main application. However, they won’t provide an optimal experience and any issues reported will need to be validated on a supported browser.
We’ll be removing this endpoint, which was deprecated in CRM 2013. You shouldn’t use this endpoint for any new extensions.
Hello CRMBlog - could you clarify two items for us:
First - Just to be clear: It is not the CRM 2013 On Prem SP1 release that drops support for SQL and Windows Server 2008 but the *next* major release after that? Also by major release after that it would not be the next smaller service pack for example, correct?
Second - Form System Deprecation: If a CRM Online *or* On Prem 2011 instance was migrated to CRM 2013 in the past how would I know the form is using the old system? To resolve this can we simply "copy" all CRM 2011 created forms and deactivate the "old" form? What about "Save As" or "Create A New Blank Form" and then "Merge". If the "new style" social pane is active on a form is that a sign a form is using the "new form system?"
I must confess, I'm a little confused.
Echoing "CRM Konrad's" question, are these changes that are happening in the Spring Wave?
Please confirm whether or not this requirement will EVER apply to CRM 2013.
On another Microsoft information Channel I just got word that this drop of support will *not* be part of the Spring Release but truly the *next" release. [My guess is the Fall 2014 Release on the roadmaps I've seen.]
All of this still impacts updates we are currently doing because it will be poor form to tell someone their upgrade/migration is complete and then inform them in 4-6 months we need to upgrade all their forms [again] or they need different server specs.
The forms question is still by big concern. How do you identify an "Old Versus New" form system form?"
Please refer to:
Update your forms to Microsoft Dynamics CRM 2013 or Microsoft Dynamics CRM Online Fall '13
1st question - Yes, that is accurate, we are calling it the Fall Release and will update this block article shortly.
2ed question – CRM 2011 forms are called “information” whereas CRM 2013 forms are called by their entity names. As part of CRM 2013, we added a feature to the form designer to allow you to copy the content of another form to the form you are working on. This was put into support form upgrade. Any new form created will be created against the CRM 2013 forms, If you copy the CRM 2011 form to a new form, it effectively becomes a custom form.
We do not currently have plans to drop Window Server 2008/r2 or SQL Server 2008 from support for CRM 2013.
However please note: Windows server 2008 and SQL server 2008 will exit extended support before then end of extended support for CRM 2013. When Windows Server 2008 and SQL Server 2008 exit extended support we will need to drop support for them in CRM 2013. Please see the Microsoft Support Lifecycle site for details on those dates.
Hi, is there any update on support for SQL Server 2014 with Dynamics CRM 2013?
Hi there, just a note I have picked up on with regards to the Kit Products. The Is Kit field is missing in CRM 2013 SP 1 now. I was not able to view it on multiple organisations from Advanced Find. I was however able to view it in SQL.
@Mayank S, one of my clients is using SQL Server 2014 and as yet we have encountered no issues. However, as far as I am aware there is no official statement that it is supported.