While assessing Upgrade of System, Key considerations:
Unsupported Code - Of JS and C# -
For On premise, can use a Code to check for references to the unsupported code.
(For Online, can use the Power-apps solution checker)
Reference to the OOB internal tables/fields that are meant to change - Example - String Map and Object Type Code should be removed/updated to use the recommended ways of the Table Name and Option set instead refer
Reports - Use Shared Data Source, to minimize repetitive steps during deployment
Number Of fields exceeding the maximum allowed - while importing solution from source
(older version)
to the upgrade instance (Newer version) - happens as newer version might have an additional set of system fields
Ensure there's no Unsupported Customization:
https://learn.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg328350(v=crm.8)?redirectedfrom=MSDN#Unsupported
No comments:
Post a Comment