Microsoft Dynamics CRM (Archived)

ReferenceError: $ is not defined

(0) Share

Report

Posted on by Community Member

Hi,

We get the following error when openening different entities (e.g. contact and opportunty).

ReferenceError: $ is not defined

at getSettings (xxxxx.crm.dynamics.com/.../pre_fieldsecuritydynamicshow)

at onLoading (xxxxx.crm.dynamics.com/.../pre_fieldsecuritydynamicshow)
at eval (eval at RunHandlerInternal (xxxxx.crm.dynamics.com/.../ClientApiWrapper.aspx:142:32), <anonymous>:1:1)
at RunHandlerInternal (xxxxx.crm.dynamics.com/.../ClientApiWrapper.aspx:142:1)
at RunHandlers (xxxxx.crm.dynamics.com/.../ClientApiWrapper.aspx:101:105)
at OnScriptTagLoaded (xxxxx.crm.dynamics.com/.../ClientApiWrapper.aspx:215:1)
at xxxxx.crm.dynamics.com/.../ClientApiWrapper.aspx:186:1

Is this a know issue? It looks like a jquery error.

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (2)

Daniel Wikell 2,360 on at

Like (0)

Report

It looks like you have a custom script (or one from a third party solution you have installed) running that depends on jquery. Check if this "ava_fieldsecuritydynamicshow"-script is loaded in the form where you experience this problem (customize the Form and click the Form Properties button).

Is the form also loading jQuery? If it is, you can try change the script load order and make sure that jquery is loaded before the ava_fieldsecuritydynamicshow script. If not, you can try and add a reference to the jquery script.

If the problem still persists I'd suggest you contact the developers of the custom script.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Aziz,

$ is selector in JQuery. So first thing need to check, whether web resource is having reference of any JQuery. If yes then make sure that JQuery library will get loaded before this web resource.

Regards,

Pranit Chavan

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Update:

1. The errors appeared after update from CRM Dynamics 2013 to 2015 (both online)

2. When I remove the script from the form onload event, the errors disappear

3. In 2013 JQuery 1.7.2 was loaded while 2015 loads jquery 2.1.1

4. So far I know, JQuery in both cases is loaded correctly and in the right order.

Kr

Was this reply helpful? Yes No
Abhishek Gupta 2,003 on at

Like (0)

Report

I to have faced the same issue after CRM 2015 update 1. I have replaced the J Query library with the latest J Query library available and it worked for me. Just give a try.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Abhishek,

Should I remove the older vesrion of the web resource (e.g. jquery_1.9.1.min.js) add the new one (jquery_2.1.1.min.js) or just replace the js file in the existing web resource?

Was this reply helpful? Yes No
Abhishek Gupta 2,003 on at

Like (1)

Report

Hi Aziz,

I did the same as you specified. I had just removed my older j query File with the latest File and it worked for me.

Was this reply helpful? Yes No
Verified answer

benPWP 65 on at

Like (3)

Report
I too am getting this error after 2015 Update 1 was applied. I opened a case with Microsoft, their solution at the moment is to re-enable legacy form rendering by going to Settings > Administration > System Settings > "Use legacy form rendering" = Yes.

They say that this will be patched in an upcoming release.

I wanted to keep the new form rendering, so in the script which is calling jQuery, i added the following:

if (typeof($) === 'undefined') { var script = document.createElement('script'); script.src = 'ajax.googleapis.com/.../jquery.min.js'; script.async = false; document.head.appendChild(script); }

This works nicely :)

Hope this helps!

Ben

Was this reply helpful? Yes No
Verified answer

benPWP 65 on at

Like (3)

Report
Even better, I discovered that jQuery is actually on the page, but the user-defined scripts are now being loaded in an iframe below where jQuery is loaded. The following is an even better fix:

if (typeof($) === 'undefined') { $ = parent.$; jQuery = parent.jQuery; }

Regards, Ben

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Ben,

Setting the "Use legacy form rendering" option to Yes worked for me.

Thnx

Was this reply helpful? Yes No
benPWP 65 on at

Like (0)

Report

That works, but the legacy form rendering is much slower than the new form rendering, and also that option will be switched off in a future update (see technet.microsoft.com/.../dn531078.aspx).

Was this reply helpful? Yes No