Partager via

Just Released: Custom Code Validation Tool for Microsoft Dynamics CRM 2015

  • Article

To help you prepare for your upgrade to Microsoft Dynamics CRM 2015, we have created the Custom Code Validation Tool for Microsoft Dynamics CRM 2015.

When using JavaScript code in Microsoft Dynamics CRM, it is possible that some code will stop working or cause an error when you upgrade. The Microsoft Dynamics CRM Custom Code Validation Tool helps identify potential problems so that a developer can fix them.

Please run this tool on your CRM instance to help identify potential issues with custom JavaScript in JavaScript libraries and HTML web resources. It will detect issues in the custom web resources that will no longer work after the upgrade is completed.

The most common issues that this tool targets are:

  • Common DOM manipulations
  • CRM 2013 Deprecated APIs

Running this tool before upgrade will enable you to identify issues and fix them prior to your scheduled upgrade so that your upgrade process can run smoothly.

Download the tool here

Comments

  • Anonymous
    January 01, 2003
    Investigating
  • Anonymous
    February 18, 2015
    The comment has been removed
  • Anonymous
    February 22, 2015
    I'm getting the same error as Art.
  • Anonymous
    February 25, 2015
    Same here
  • Anonymous
    February 26, 2015
    The comment has been removed
  • Anonymous
    March 03, 2015
    Microsoft is aware of the issue and an update will be made available to the Download Center shortly.
  • Anonymous
    March 04, 2015
    Define "Shortly"
  • Anonymous
    April 03, 2015
    Okay, Convergence 2015 is over, is a fix or workaround available yet?
  • Anonymous
    April 13, 2015
    I had the same issue as Art. I found that it was tied to a specific web resource. I was able to get around this by removing the top web source result from the environment prior to scanning.

    Specifically, it was a *.html resource causing me issues. Since I only wanted to scan *.js resources, this wasn't a huge problem... just a pain.
  • Anonymous
    April 13, 2015
    I had the same issue as Art. I found that it was tied to a specific web resource. I was able to get around this by removing the top web source result from the environment prior to scanning.

    Specifically, it was a *.html resource causing me issues. Since I only wanted to scan *.js resources, this wasn't a huge problem... just a pain.
  • Anonymous
    May 26, 2015
    Having the same issue. Has a fix been released since March 3rd?
  • Anonymous
    August 19, 2015
    Same issue. Doesn't look like there is anybody checking these comments. And I am unable to figure out which resource could be causing an issue, so that won't work for me.
  • Anonymous
    August 27, 2015
    New tool being published soon. In the meantime please contact support to get the tool immediately.
  • Anonymous
    September 23, 2015
    Hi Jesper, can you please let us know when this new version of the tool will be published? We're looking forward to it. Your last post on this subject was from August 27th but the tool on the Microsoft Download Center website still appears to date from March 10, 2015.
  • Anonymous
    June 10, 2016
    Current version still contains given key exception. As there is no tool for validating an upgrade to 2016, this is the only tool that people can use and it's not even fit for purpose!!