web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM2016 stuck "Lo...
Microsoft Dynamics CRM (Archived)

CRM2016 stuck "Loading Business Logic" for Contact. Navigating away results in JS error.

(0) ShareShare
ReportReport
Posted on by Community Member

This is a 2016 on Prem with update 1. Updated from 2013 on Prem.

When navigating to Contact, if going to our custom form, the page will get stuck "loading business logic." If you attempt to navigate away, it will throw a JS error "Unable to get property 'addOnChange' of undefined or null reference". We have multiple custom forms, but only 1 of them produces this issue. This error seeds from dynamics code when using dev tools in IE.  Error message refers to this line:

$v_3.addOnChange(Mscrm.TurboForm.Control.CustomScriptsManager.get_instance().getHandler($v_2))


I have found a few posts regarding similar issues and I have attempted their resolutions but no luck. 

  •  All Javascript events have been removed from form
  •  Business rules are off
  •  Show Navigation Items is On
  •  Added/ removed fields and re-published 
  • Browser data cleared

Legacy Form Rendering DOES work, but I don't think this is a sound solution, as I would like to get the most out of using the new rendering model for performance and future stability. 


Any thoughts or suggestions for what to try next? Thank you.

*This post is locked for comments

I have the same question (0)
  • Tanguy TOUZARD Profile Picture
    Tanguy TOUZARD 687 Most Valuable Professional on at

    Is there any field in the form designer that does not show the name of the attribute? I remember having some fields without attribute name making the form behaves like you described

  • Community Member Profile Picture
    Community Member on at

    Thanks for the suggestion. I checked but the names seem to all be there. It's almost an exact copy of another form we have that works just fine. This one just has some of the fields unlocked for editing.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    This has been resolved. Turns out, only on a custom form, missing parentcustomerid causes this issue in 2016.  Debugging the error in IE brought me to that field.

  • Community Member Profile Picture
    Community Member on at

    Hi Casey!

    I am facing the exact same issue, only for me it is the incident form and not contact. Could you please go a little more in details what you did to find the field that was causing the problem for you?

    Thanks in advance

    Daniel

  • Community Member Profile Picture
    Community Member on at

    Hi Daniel,

    The way I discovered the field was through debugging the page in IE. If the page was stuck "loading business logic" and I tried to navigate away, I would get an error. I tracked that error through IE's debugger and came across the field name eventually. Turns out, it was a required field that was not on the form. In CRM2013, CRM did not complain. We had some logic that would deal with required fields automatically, but they never needed to reside on the form. So I added the field to the form and just left it invisible. If your issue is the same, I would say check the required fields for the entity and see if any are missing from the form. Is this a custom form? I did not have an issue on the OOB form. I know there are a few other solutions out there but none of them worked for me. Hope this helps, let me know I can assist anymore.

  • Community Member Profile Picture
    Community Member on at

    Hi Casey,

    Thanks for your quick reply! This issue occures in one of the two OOB forms for the incident entity: the original one that came from CRM 4.0 / 2011 called "information" is working fine, the one called "case" that came with CRM 2013 has the issue. I have seen the other solutions out there two, but as for you they did not work for me either.

    As I was having the exact same error

    $v_3.addOnChange(Mscrm.TurboForm.Control.CustomScriptsManager.get_instance().getHandler($v_2))

    I was really hoping that your solution would work for me too, but I added every field that there is to the form and still get that error. I am quite stuck here...

    None the less, thank you very much for shareing your solution.

    Daniel

  • Community Member Profile Picture
    Community Member on at

    If you can, see if you can dig into the browser debugger a bit deeper and I better you should come across a field name. I think the script is attempting to pull data that it cannot find or is somehow prevented from being accessed. From there you try to see what is different about that field that may be causing it to break. If you turn off the turbo forms and use the old rendering, does the page load fine? Mine would. As a temporary solution, that works, but the old rendering platform will only be supported for a short while.

  • Suggested answer
    Aleksandr Rogov Profile Picture
    Aleksandr Rogov 35 on at

    Hi all,

    I've just had a similar issue with one of my custom entities. First of all, error: "Unable to get property 'addOnChange' of undefined or null reference" was only shown when I opened F12 console and in IE (11) ONLY. F12 console not only showing the error message but also where it happened, in my case it was in "JsProvider.ashx". If you click on it, IE will navigate you to the line where the error happens. Place a breakpoint there then navigate away and come back (or just refresh a page) to execute a trigger.

    There is an object called "$v_3", this object is a reason why the error occurs, because at some point it becomes "null".

    So, you need to click Continue (F5) and at each breakpoint check $v_3 object until you see that it's "null". When it's "null" check another object "$v_2", this object contains the data about the control that is processed at that point, you need to look for $v_2.AttributeName property: this property will contain the name of the attribute and, most probably, this attribute (field) is absent on the form.

    2017_2D00_07_2D00_14_5F00_11_2D00_01_2D00_20.png

    Go to the form and check if that field is on the form, if it's not there add it to the form and then save and publish. Now the error should go away and the record should be opened successfully.

    Hopefully this answer will solve your problem.

  • Community Member Profile Picture
    Community Member on at

    Hi,

    I have exactly the same issue with my $v_3.AddOnChange. Can you be more specific Alexander please? What was your attribute exactly? How could you find it? 

    Thank you,

    Edit : I found the $v_2.AttributeName property and it's the currency, it's already on the form with a lock... :( 

  • Aleksandr Rogov Profile Picture
    Aleksandr Rogov 35 on at

    Hi Fabiien,

    You need to "F5" until you see that $v_3 is null before checking $v_2.AttributeName. Was it null when you checked $v_2.AttributeName?

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans