1) Use an external JavaScript file while doing development. It will save you a lot of time. Regularly you make a code change and then you need to save and publish every time you want to retest. Yes, the preview feature is helpful some of the time, but it is still very time consuming. Using an external file will also allow you to leverage Visual Studio which offers IntelliSense and syntax checking.
Add this code to your onload. It loads a JS file from within your ISV folder. It uses a query string parameter to prevent caching and it waits until the dom is loaded before it executes the code.
var head = document.getElementsByTagName('head')[0];
var script = document.createElement('script');
script.type= 'text/javascript';
script.src= '/ISV/Entity/accounttesting.js?noCache=' + Math.random();
script.onreadystatechange= function () {
if (this.readyState == 'complete' || this.readyState == 'loaded')
{
document.OnLoadCode()
}
}
head.appendChild(script);
Second, you can add calls in your OnSave and OnChange events to call code in the JavaScript file. This will allow you to do all development in the one file.
OnSave: document.OnSaveCode();
OnChange of account name: document.OnChangeCode_AccountName();
Third, add a file name accounttesting.js to your /ISV/Entity folder under the website folder. It will contain the following code.
document.OnLoadCode = function()
{
alert("OnLoad code");
}
document.OnSaveCode = function()
{
alert("OnSave code");
}
document.OnChangeCode_AccountName = function()
{
alert("OnChange of Account Code");
}
// other functions
Last, start testing. Any time you make a code change to the file you can refresh the account screen (F5) and the newest code will be executed. Instant results!!!
Disclaimer: You should only use this for development. After you have tested your changes using this method you should copy the code back into the OnLoad and comment out the code that loads the JavaScript file. Keeping the file in your OnLoad will save you time and headaches in deployment. Plus, this is not supported.
2) Use the debugger statement in your code if you want to walk through code. You are able to leverage Visual Studio to analyze variable values as you execute your code. Very useful!
First, within Internet Explorer, uncheck “Disable script debugging (Internet Explorer)” and “Disable script debugger (Other)”
Next, add following code before any code you would like to debug.
debugger;
3) Use a helper library for calling the CRM web service through AJAX. Calling the CRM web service requires you to work with the XML request using string concatenation which is very error-prone. The libraries provide an object-oriented API to return data from CRM. They also provide better error handling to help you troubleshoot errors
You can use my helper objects Click Here. Ascentium has one as well Click Here. Their library uses fetchxml while mine uses RetrieveMultiple.
4) Use Intellisense to help prevent mistakes as you code. The book CRM as a Rapid Development Platform comes with a excellent Intellisense generator for Visual Studio. http://www.thecrmbook.com/Video/Customization/EnableCRMJavascriptIntellisense/viewvideo.aspx. It is well worth the 50 dollar investment.
You point the generator application against your instance of CRM and it generates JavaScript files for you to reference in your JS file. Now you have Intellisense. No more copy and pasting the field name from the forms window to make sure you don’t mis-spell it. No more bugs because you spelled the word crmForm as crmform.
5) Follow the DRY principle. Don’t repeat yourself. If you need to hide a field both onload and when a specific dropdown is selected, don’t copy and paste the code around. Add functions to OnLoad and call the function wherever you need to. Also, as you find useful code, such as hiding and showing fields, create functions for them and re-use them from project to project.
6) Use try catch statements where possible. Depending on your browser setings, it may be hard to determine what error is actually being thrown, especially in OnLoad. Catching the error message and displaying an alert will help save time while troubleshooting errors.
try
{
// Implementation here
}
catch (er)
{
alert(er.message);
}
First posted by Andrew Zimmer of Inetium
Comments