Archive for October 2014

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

iFrames and Relative Paths

I ran into this issue again and although I am sure I write about it before, I can’t find a reference to it. The Scenario In Dynamics CRM 4.0 it was quite common for companies (on-premise) to have custom ASP.NET pages that were shown within the context […]

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

Upgraded Dynamics CRM 4.0 Anomaly

One of my SnapShot! customers ran into what could be one of the strangest anomaly’s this week that I thought I would document here, so that other people (including myself) can find it. They were running SnapShot! against a Dynamics CRM 2011 organization as they were prototyping […]

Read more
Page 1 of 212