Whereas the resolution of some issues was given in “Resolve Breaking Script Issues When Upgrading Microsoft Dynamics CRM” article, we had to fix some other problems which were out of the scope of that article.
Here we list the errors we faced and the ways to resolve them by applying the following changes:
- В XMLHttpRequest function error
Change: var XmlHttp = CreateXmlHttp();
to: var XmlHttp = Mscrm.XmlUtil.createXmlHttp();
Change: window.showModalDialog(serverUri + ‘?DialogId=’ + dialogId + ‘&EntityName=’ + typeName + ‘&ObjectId=’ + triggerId , null, ‘dialogWidth=615,height=480,resizable=1,status=1,scrollbars=1’);
to: window.showModalDialog(serverUri + ‘?DialogId=’ + dialogId + ‘&EntityName=’ + typeName + ‘&ObjectId=’ + triggerId , null, ‘dialogWidth: 615px; dialogHeight: 480px; resizable: yes; status: yes, scrollbars:yes;’);
- crmForm error
Change: crmForm.all.ut_name.DataValue = name;
- Ribbon missing
We also faced an issue with Ribbon missing after CRM Online December 2012 Update. To resolve it, we had to disable Form Assistant (the process is described in detail in the article “A script error occurs or the ribbon fails to load in the Case, Product, or Service Appointment entities in Microsoft Dynamics CRM Online or after applying Update Rollup 12 in On Premise”).
We’ll be glad if you find our solutions for CRM December 2012 update issues helpful.