Archive for the Conversion Strategies Category

JavaScript Upgrade Strategies: The Results

So this is the conclusion to my JavaScript Upgrade Strategies series. So now that I have told you how to do all of these things, how about asking why? Here is why: Reduced code-base Reduced maintenance Faster user experience   Real Data Points Here are the results […]

Read more

JavaScript Upgrade Strategy #16: Testing, Testing, Testing

Nothing beats real testing to shake out the bugs on a newly migrated system. These should include: Real users Real data Actual processes This should be of no surprise to anyone, but the idea that having real users test the system is far better than just have […]

Read more

JavaScript Upgrade Strategy #15: Consider disabling your plugins during testing

As you are migrating and testing your code, it may be a good idea to disable any plugins that fire when you are creating and updating a record.  This allows you the freedom to test your JavaScript without having to worry about other system components causing issues […]

Read more

JavaScript Upgrade Strategy #14: Minification

Minification is the process of reducing the amount of space a JavaScript file occupies by removing things like formatting and comments and overall rewriting the code to take up less space. This generally gives you a slight gain in performance because smaller files are faster to download […]

Read more

JavaScript Upgrade Strategy #13: Remove Unused Web Resources

Speaking of feature creep, web resources are one of the few system-level data items that can sort of build-up over time, if not properly maintained. Again, this happens because of a change in business direction, a rewrite of functionality, etc. Most of the time, these unused web […]

Read more

JavaScript Upgrade Strategy #12: Refactor, Refactor, Refactor

I really cannot emphasize this enough, but this is your chance to fix all of your code and architecture issues. You are taking the time to, in most cases, upgrade your hardware platforms, move the databases around, etc., so why would you not spend time fixing code […]

Read more

JavaScript Upgrade Gotcha #5: = does not equal ==

I run into this occasionally when converting Dynamics CRM 4.0 JavaScript into the 2011 object model. Consider this piece of code: if ((crmForm.all.new_field1.DataValue >= 3) && (crmForm.all.new_field1.DataValue <= 10)) { sitetotal = 2; } else if (crmForm.all.new_field1.DataValue > 10) { sitetotal = 3; } else if (crmForm.all.new_field1.DataValue […]

Read more

The value of using Visual Studio to edit your Dynamics CRM JavaScript

As I have stated previously, if you are not using Visual Studio to edit your Dynamics CRM JavaScript, you are doing yourself a huge disservice. Consider this code:     Can you spot the problem? Visual Studio and Resharper did. Notice the blue line under Industrytotal? It […]

Read more

JavaScript Upgrade Strategy #11a: Code Not Configuration

As with many things in Dynamics CRM Development, there are more than one way to do the same task.  Take the addition of an OnChange event handler, for instance.   A Little Background Here is how we would normally configure an OnChange Event that automatically formats a […]

Read more

JavaScript Upgrade Strategy #11: Configuration vs. Code

Starting with Dynamics CRM 2011, we have the ability to hide form elements (fields, sections, tabs) by using either JavaScript or by setting the Visible by Default property using the properties dialog for each individual form element. If you are upgrading your JavaScript from Dynamics CRM 4.0, […]

Read more
Page 1 of 41234