Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In CRM 2011, the browser Chrome version 66 generate an error when I select a record in a lookup field writing the name and pressing tab (not selecting record in the popup Window).
How can I fix this problem?
Make sure you have all the rollups for CRM 2011 installed which provides supported for browsers. Or you can try to run chrom on compatibility mode to check if works fine or not
Yes, last rollup is installed.
Exists a compatibility mode in Chrome? How can I execute it?
FYI, this Chrome 66 problem also exists in CRM 2013 SP1 v126.96.36.1991 but the problem does not exist in CRM 2013 SP1 UR5 v188.8.131.52. I don't know which rollup between 1 and 5 fixes the Chrome 66 problem. 2013 SP1 UR2 did have a Lookup field fix for Chrome 38 which may or may not be related. Do they keep CRM 2011 updated for browser compatibility like they do with 2013?
What error do you see?
Do you have any code in the onChange event of the lookup control that is generating the error?
If you do, can you debug the onChange function and go step by step (line by line), to verify that there is no error in the backend code, or anything that is not supported by Chrome v66.
Hope this helps.
I don't have any code in the onChange event.
For example: when i choose the customer in a Quote (CRM is in italian version)
with CRM Diagnostics Tool i catch this log:
>System.NullReferenceException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #21F977D9: System.NullReferenceException: Object reference not set to an instance of an object.
> at Microsoft.Crm.Application.WebServices.LookupService.RetrieveItem(Int32 typesArray, String bindingColumns, String additionalParameters, String values, Int32 positions, Boolean resolveEmailAddress, String savedQueryTypeParameter, String defaultViewId, Nullable`1 defaultViewType, String defaultViewFetchXml, String defaultViewLayoutXml, String guidValues, Boolean sortResults)
>MSCRM Error Report:--------------------------------------------------------------------------------------------------------Error: Object reference not set to an instance of an object.Error Message: Object reference not set to an instance of an object.Source File: Not availableLine Number: Not availableRequest URL: srv-crmdev/.../LookupService.asmxStack Trace Info: [NullReferenceException: Object reference not set to an instance of an object.]at Microsoft.Crm.Application.WebServices.LookupService.RetrieveItem(Int32 typesArray, String bindingColumns, String additionalParameters, String values, Int32 positions, Boolean resolveEmailAddress, String savedQueryTypeParameter, String defaultViewId, Nullable`1 defaultViewType, String defaultViewFetchXml, String defaultViewLayoutXml, String guidValues, Boolean sortResults)
From what I can tell, this problem is out of the control of anyone but Microsoft.
I compared CRM 2013 SP1 (bad) to 2013 SP1 UR5 (good). In the bad version's call to .../LookupService.asmx, the POST message body contains an XML soap:Envelope whose soap:Body element is missing the lookupValues element.
MDN shows that Chrome 66 got Array.prototype.values() which is why the problem cropped up this week.
Seems like this might be an issue with the latest release of Chrome 66.
I just encountered a similar issue on a D365 (8.2) implementation, where in the business process flow when you type the text instead of clicking on the lookup button it reverts back to your typed text. Although it is not showing an error message, the lookup value is showing the warning (as not accepted the entered option).
This only happens when there are multiple options starting with the same name of course.
This was not happening in Chrome v65.
If I find out a resolution I will post.
Meanwhile, thanks for the support
The most recent CRM 2011 update I see is from 2014 (https://support.microsoft.com/en-us/help/2555051/microsoft-dynamics-crm-2011-updates-and-hotfixes).
Mainstream support ended in July 2016 although it is in extended support until July 2021 (https://community.dynamics.com/crm/b/zero2ten/archive/2013/12/11/microsoft-dynamics-crm-support-lifecycle).
I would be worried that Microsoft will never update CRM 2011 to fix this Chrome compatibililty issue.
@Matteo Did you get the solution ? I'm facing the same issue :(
No, I'm sorry... :-(
We fixed this issue by disabling ES Array Prototypes via:
We are using Chrome version: 66.0.3359.181
@IrateAdmin thank you so much. It is working like a charm.
Thank you very much IrateAdmin. It works!
Business Applications communities