Jscript unable to get property ‘$o_3’ of undefined or null reference CRM 2015 Update1.0

This error got introduced on CRM 2015 after upgrading to 1.0.



Error Message:

unable to get property ‘$o_3’ of undefined or null reference


This error caused due to unsupported customization in the Java script on form load. The new form rendering mechanism does not recognise this script. using document.getElementById is unsupported. If you are using pre-filter default view on form load, this error will pop-up.

Note that this error only occurs when you turn on the “Use Legacy form rendering”

CRM2015 Use Legacy Form rendering

You only need to turn on this form rendering, when there is lot of JS functionality is used and not behaving in intended manner.


If you are trying to add a custom view to the lookup and set that as the default, then you can use the

Xrm.Page.ui.controls.get(“[tablename]”).addCustomView(viewID, “[tablename]”, “[viewname]”, “[fetchXMLString]”, “[TSAlayoutXMLstring]”, true);


About Patric Antony

As a Microsoft Dynamics CRM consultant contribute professional service in the area of Functional and Technical consulting, Solution Design, Data Migration, Testing, Integration with AX, BizTalk, SharePoint and other external IVR, .net, Java based applications. Deft in conducting scope analysis, business study, requirements study, design, development, testing and implementation, as well as rendering application enhancement support to the client. CRM implementation More than 7 Implementation in CRM Online and On-premise deployment. Versions CRM 3.0, CRM4.0, CRM 2011, CRM 2011 Online, CRM 2013, CRM2015, CRM2016 Online Enjoying CRM Consulting ,Working with CRM since 2006.
This entry was posted in Uncategorized. Bookmark the permalink.

5 Responses to Jscript unable to get property ‘$o_3’ of undefined or null reference CRM 2015 Update1.0

  1. Laurent says:

    I get the same error when using addpresearch & removepresearch functions.
    Do you have a clue for me?

    • This error occurs only when you turned on the legacy form. Set it back to turbo form.

      You will find this option under Administration>>System Settings>Use legacy form rendering: Set to No. Turbo form loading performance is much better than legacy form loading.

      If you must use legacy form settings, you will need to rewrite your JS to suit UR1.0.
      Any DOM access JS is not supported in CRM2015 update 1.0.

  2. Add this script before calling preFilter function. this will resolve the issue.

    Xrm.Page.getControl(“EntityName”)._control && Xrm.Page.getControl(“EntityName”)._control.tryCompleteOnDemandInitialization && Xrm.Page.getControl(“EntityName”)._control.tryCompleteOnDemandInitialization();

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s