![]() ![]() After you have created an upgrade codeunit to handle table changes, you can use it when you upgrade data from an earlier version of Dynamics NAV to the current version. ![]() ![]() For more information about destructive changes, see Handling Destructive Changes With Table Schema Synchronization. You implement upgrade codeunits when you make destructive changes to tables in Microsoft Dynamics NAV Development Environment. Instead, you want to use it somewhere else in the new application. For more information, see Updating Custom Report Layouts by Using Upgrade Codeunits.Ī typical example of when to use an upgrade codeunit is when you remove a field from a table definition and you do not want to lose the existing data in the business data table. Provides instructions for updating custom report layouts to dataset changes. Provides the logic for migrating existing data in the business data table from the old format to the new format after schema synchronization. For more information, see Synchronizing Table Schemas. Provides instructions for how to handle data changes to a table during schema synchronization. An upgrade codeunit serves the following purposes: Upgrade codeunits migrate existing business data from the old table structure into the new table structure. You use upgrade codeunits when you make changes to a table definition, either from the Microsoft Dynamics NAV Development Environment or during an upgrade. ![]()
0 Comments
Leave a Reply. |