Hi Readers,
I hope you are doing well and had a great weekend!
Since a lot of changes have been happening since the release of Business Central and everyone is looking for an upgrade and want to move to SaaS, i.e, Microsoft NAV (from any version) to Dynamics 365 Business Central. I would like to talk about some checkpoints.
Before you jump into the data, application and PowerShell commands, there are a few important points that you should consider. You can also call them as Prerequisites or precheck. Following are the points:
1. Codeunit 1 (ApplicationManagement) has been deprecated and replaced and new ‘system’ codeunits has been introduced. No functionality has been removed by this change. All system method triggers, event publishers, and their code have been moved to other codeunits.
2. MenuSuite not used for page and report search. In Business Central, instead of using the MenuSuite, pages and reports are made searchable by setting properties on the page and report objects themselves, specifically the UsageCategory property, and optionally the AccessByPermissions and ApplicationArea properties. The UsageCategory property corresponds to the DepartmentCategory property on MenuSuite items linked to page and report objects.
3. Dynamics 365 Sales integration should be performed, if an Integration is involved.
4. New and changed application features, for this there a several new and changed application features available in Business Central April 2019 for users, administrators, and developers. You will have to perform an application code upgrade, not just a technical (platform) upgrade.
5. Changes to profiles in the CRONUS International Ltd. demonstration database and promoted actions. To ensure that users are not disrupted by these changes, it is recommended that administrators and partners who are upgrading a customer to Business Central April 2019, review the layout of promoted actions when combined with their own code and profile customization.
6. Names of variables – If the name of the variable is the same as Business Central keyword, change it before the upgrade.
7. If you are upgrading a solution that depends on functionality that is deprecated or changed in the default version of Business Central, you must verify that the upgrade codeunits migrate data correctly.
8. Business Central will have Deprecated fields and fields marked as obsolete. This will be handled by Upgrade toolkit.
9. Upgrade Codeunits - When you introduce changes to the database schema, Business Central will check if these changes are destructive or not. If the database check indicates that the change may lead to data deletion, such as if you are dropping a table column so that the contents of that column will be deleted, this is considered a destructive change. You will be prompted to handle the situation using upgrade codeunits.
10. If a company name includes a special character, an error may display during the upgrade.
11. All columns of system tables should be in English.
No comments:
Post a Comment