Archive for the Conversion Strategies Category

JavaScript Upgrade Strategy #10: Convert Unsupported Code

Again, since we are in refactor mode, now is the time to fix all of your previous decisions.  Some, or in some cases, many of those decisions involved using unsupported JavaScript. In the days of Dynamics CRM 4.0, we had to do a lot of unsupported code […]

Read more

JavaScript Upgrade Strategy #9: Replace SOAP Calls

When developing in Dynamics CRM, sooner or later you will find a requirement to perform some type of database operation. In Dynamics CRM 4.0 we had to the choice of creating raw SOAP requests or by using a library from Ascenitum (later Avanade), to perform these operations. […]

Read more

JavaScript Upgrade Strategy #8: Eliminate Single-call Methods

When your Dynamics CRM 4.0 JavaScript is converted to the Dynamics CRM 2011 object model, all of the events are consolidated into a single web resource that may look something like this:     As you can see from each of the OnChange events above, you can […]

Read more

JavaScript Upgrade Strategy #7: Code Consolidation

Continuing on our refactor process, we enter the code consolidation phase. This includes the following processes:   Remove duplicate functions One of the features of Transformer! is to identify duplicate functions when performing the conversion process but you can always just hunt these down manually, if necessary.  […]

Read more

JavaScript Upgrade Strategy #6: Code Removal

One of my absolute joys when upgrading a Dynamics CRM organization from 4.0 to 2011 is the chance you get to actually remove JavaScript from your system. Remember: Code that you do not have, is code you do not have to maintain. Part of the consolidation process […]

Read more

JavaScript Upgrade Strategy #5: Web Resource Organization

When designing or re-designing JavaScript Web Resources, there are a few practices that I like to follow:   One web resource per entity Create one resource for each entity. This resource will contain JavaScript functionality related specifically to that entity.   One web resource per entity ribbon […]

Read more

JavaScript Upgrade Strategy #4: Reorganize your functions

Here is a fairly typical view of the function tree of a Dynamics CRM 4.0 organization for the Account entity:     As you can see, we have our OnLoad function with various functions embedded within it.  This was done so that those functions would be available […]

Read more

JavaScript Upgrade Strategy #3: Use Visual Studio (with add-ins)

One of the best practices a Dynamics CRM developer can follow is to use Visual Studio to edit your JavaScript.  Combine the basic functionality with an add-in like Resharper, and you have a very productive development environment.  Here’s why: Intellisense Visual Studio provides both intellisense and the […]

Read more

JavaScript Upgrade Strategy #2: Upgrade your object model

After you get your development up and running, one of the first things you need to do is to convert your JavaScript code-base from the Dynamics CRM 4.0 object model to the CRM 2011 object model.  Let us review that process:   Tools If you are not […]

Read more

JavaScript Upgrade Strategy #1: Create a test environment

Upgrading your Dynamics CRM organization from version 4.0 to anything newer can be a lot of work. The amount of work will depend on how much custom code (JavaScript and Plugins) that you have installed. This is where having a test environment pays for the time and […]

Read more
Page 2 of 41234