Jscript Analysis Steps
1. Export Jscript with a tool.
http://blogs.infinite-x.net/free-utilities/
2. Sort out
JS by size and type to see the effort. JScripts that are on change are usually
the shortest.
3. Make a
list of all jscript codes.
Entity
|
Attribute
|
Event
|
Comment
|
account
|
|
onload
|
SW filtered lookup -
replace w/ OOB; user role web svc call
|
account
|
|
onsave
|
Minor - account name
validation
|
account
|
new_slcustomertype
|
onchange
|
Minor
|
account
|
customertypecode
|
onchange
|
Minor
|
account
|
address1_postalcode
|
onchange
|
Yahoo Web svc call to
populate City/State from Zip - Remove
|
4. Verify
that there are no unsupported customizations present.
5. Identify
what base xml or current customizations can be replaced by native CRM features
Pay attention to:
o filtered lookups
o field level security scripts
o forms with sub-grids
o custom audit
6. Create a
list of unsupported customizations and plan to migrate your scripts from using crmForm
to Xrm.Page.
You can read more about migration at http://msdn.microsoft.com/en-us/library/gg509046.aspx
7. Convertor jscripts,
using the tool below.
http://crm2011scriptconvert.codeplex.com/
Remove jscript -> Upgrade Dev -> Bring back converted Jscript -> Clean -> Test
Cleanup:
-
Remove duplicated functions and use library to call one function
at each entity.
After a trial upgrade test every entity.
Resources:
http://technet.microsoft.com/en-us/library/gg554717.aspx
http://blog.sonomapartners.com/2011/04/upgrading-to-crm-2011-our-story.html
http://weblogs.asp.net/pabloperalta/archive/2010/11/01/step-by-step-installing-crm-2011-on-premise-and-migrating-from-dynamics-crm-4-0-32-bits-on-premise.aspx
http://crmentropy.blogspot.com/2011/10/upgrade-crm-4-to-2011-for-itdiots.html
No comments:
Post a Comment