CRM 2015: Organization import stops because of JavaScript errors? Check out this workaround!

crm import errorWhen you’re importing your organization, you might find that your import process comes to a dead stop because the verification found JavaScript code that is not compatible with CRM 2015. However, you might want to import your organization regardless, and work with the JavaScript code once it’s up and running (for the most part).

Fortunately, there’s a workaround for this. It’ll require fiddling a bit with the registry, but it’s no biggie and it’s something I learned from a Microsoft engineer.

To allow our import to continue, we needs to add the IgnoreChecks registry key to the computer that is running Microsoft Dynamics CRM.

  1. Click Start, click Run, type regedit, and then click OK.
  2. In the registry, locate the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM.
  3. Right-click MSCRM, point to New, click DWORD Value, and then type IgnoreChecks.
  4. Double-click IgnoreChecks, and then type 1 in the Value data field.

That’s it! Now run again your import process and feel happy that you got this stumbling block out of the way. Note that although you will get the error message again, the Next button will not be grayed out, allowing you to continue with the import process.

However, don’t forget to fix your code! This is useful when yo know that the failing code is somewhat isolated and will be hit only on particular occasions. As always, follow this at your own risk. Worst-case scenario would be that you need to fix your code and then re-import your organization.

Have fun!

Advertisements
Tagged , ,

4 thoughts on “CRM 2015: Organization import stops because of JavaScript errors? Check out this workaround!

  1. Casper says:

    This dosent work for me at all. After fixing the registry, I still get the same error when importing Organization.

    Like

    • josekercado says:

      Interesting. Same JavaScript related error, or a different one? I will double-check today in my machine and get back to you.

      Like

    • Casper says:

      UPDATE:
      Sorry, it works now, I just diodnt see earlier that it was possible for me to continue the import after I’ve recieve the error message.
      My import still unsuccesful. I get this error: “PArent report already links to another report with the same name”. I will look into that now, but thanks for the registry tip

      Like

      • josekercado says:

        Great! I’m glad that worked out for you. I’ll edit my post to include the fact that you’ll get the error message anyway. I honestly had forgotten that. Good point. Thanks!

        Like

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: