Archive for the Upgrade to CRM 2011 Category

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

Reviewing the Dynamics CRM 2013 LegacyFeatureCheck Logs

Here is the detail of that error: Some plug-ins or custom workflow activities in your system appear to be using the Microsoft CRM 4.0 SDK. Use of the Microsoft CRM 4.0 SDK is not supported in this release. For information about how to upgrade custom code, refer […]

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

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

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

JavaScript Upgrade Gotcha #4: The .title property

The .title property in JavaScript is used by Dynamics CRM 4.0 to display a tool tip when you hover a mouse over the field. Here is an example:   crmForm.all.new_name_c.title = "Please validate their legal name.";   Unfortunately, there is no equivalent within Dynamics CRM 2011 so […]

Read more

JavaScript Upgrade Gotcha #3: The .style property

There are certain cases where it is necessary to customize the CRM user interface to perform a specific action or to inform the user of a specific condition or alert, or whatever. This was mainly accomplished by changing the .style property of a field. Such actions were […]

Read more

JavaScript Upgrade Gotcha #2: Using the JavaScript eval method

The use of the JavaScript method eval is considered to be bad coding practice by most of the JavaScript Technorati. That doesn’t stop people from using it, and it makes automatic conversion verify difficult. Consider this code:   this.FieldName1 = "name"; eval(‘this.Field1 = crmForm.all.’ + this.FieldName1);   […]

Read more

JavaScript Upgrade Gotcha #1: The .id property

Consider this code segment: var oField = executionObj.getEventSource(); if (oField.id == “new_field1” || oField.id == “new_field2”) { // do something } This uses the JavaScript .id property to retrieve the field name. Since this type of code can represent both form controls as well as data items […]

Read more

New Upgrade Tool Released: Kill Plugin

There are occasions which some of us may experience during or shortly after the upgrade of a Dynamics CRM 4.0 system to CRM 2011 where we discover we have plugins that cannot be removed by the Plugin Registration Tool. Most of the time this is caused by […]

Read more
Page 1 of 41234