Dynamics CRM lookup fields fail with Chrome 38
Chrome 38 has recently been released and is available as an update for your Chrome browser. We have identified an issue with this version preventing lookups to resolve or save correctly in Microsoft Dynamics CRM forms. This occurs on CRM 2011 and 2013.
Update: Chrome 38 version 38.0.2125.111 will resolve this issue.
A Knowledge Base Article has been created with additional information:
Comments
-
Looks like this issue has been handled in Version 38.0.2125.111 m of google chrome?
We have tested this on prem (CRM 2013 SP1 UR 1) and (CRM 2013 SP1).
-
Sorry for the delay. For CRM Online, this will be included in CRM Online Service Update 6. For On Premise, there should be a fix available in the next couple weeks. I do not have an exact release date yet.
-
in 2011 it seems to be due Chrome 38's partial support for ECMAScript 6 which is breaking a private function (pushCommandParameter) in the RemoteCommand function (Global.js), you can fix it but it is unsupported...
-
We have an issue with Dynamics CRM not allowing sales territories to be assigned to opportunities or organisations. This is consistent whatever browser we use. The error message received reads:
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.FormatException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #B3EB9A8EDetail:
-2147220970
System.FormatException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #B3EB9A8E
2014-10-23T11:13:01.1334167Z
-
We have seen the same issue with failed lookup's in IE 11. We have also had some failed login with a "Server Error" message. Are these issues being addressed?
-
-
Hello Aaron,
Do you know if this issue is going to be addressed in a future CRM rollup? Or is it Chrome that needs to launch a hotfix for this?
Regards,
Sven
*This post is locked for comments