Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Enter Update Rollup 15 - A Fix:
To address this scenario, Update Rollup 15 again alters the way script library files are loaded to ensure a reliable behavior and address dependency constraints. While script libraries now load in their intended order, the libraries are treated as dynamic script blocks making for an inconsistent debugging experience across browsers (debugging in Chrome? You won’t see them anywhere, although you can still do live debug by stepping into the functions or forcing a breakpoint in your code).
Form script load behavior by update:
Browser Debuggers: Dynamic script content is handled differently across the various browser debugging tools and even between versions. In the case of Chrome’s debugging tools, you won’t see dynamic script content at all. But have no fear! We’ll address circumvent this roadblock by simply traversing up the call stack by one call. Instead of breaking directly into your function, we’ll start from the point where CRM for script calls custom functions, then step into the custom function. These calls originate from FormScript.js.aspx.
Note: Another option is to use the debugger statement – by placing it anywhere in a script file it will tell the browser to force a breakpoint and pull open your debugger (as long as script debugging is enabled). This is not a desirable outcome for production code, so I suggest reserving this technique only for debugging in development environments. The remainder of this article walks through how to debug without using a debugger' statement, which should be appropriate in all deployment scenarios.
Debugging script libraries: Previous to UR15, you could simply launch the browser debugging tool, look for a named Web Resource file in the scripts list, and easily set a breakpoint to begin live debugging. In UR15, the process changes slightly:
That’s it! Hopefully, these tips have helped your post-UR15 script debugging efforts (and avoided an unnecessary headache). If you have further technical questions about how to debug, post comments or click email blog author. I am contemplating the creation of a video to walk through three or four common CRM debug scenarios. If you would find this valuable, please provide that feedback. As always, our team of Dynamics CRM PFE’s and Dynamics CRM Developer PFE’s are here to help, either remotely or onsite:
Thanks for reading! Sean McNellis
Follow me: @seanmcne
Microsoft Premier Field Engineer
Business Applications communities