{"title":"Resolving Compilation Errors When Converting a Dynamics NAV 2018 Database","url":"https://jonas-paprotka.de/docs/dev-itpro/upgrade/resolve-compile-errors-when-converting-dynamics-nav-2018-database/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/resolve-compile-errors-when-converting-dynamics-nav-2018-database, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/resolve-compile-errors-when-converting-dynamics-nav-2018-database","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to resolve errors when you convert a Dynamics NAV database to the Business Central format.","date":"2024-04-18","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Resolving Compilation Errors When Converting a Dynamics NAV 2018 Database","slug":"resolving-compilation-errors-when-converting-a-dynamics-nav-2018-database","at":0,"chars":3566},{"level":2,"title":"Compilation Errors","slug":"compilation-errors","at":293,"chars":3273}],"text":"# Resolving Compilation Errors When Converting a Dynamics NAV 2018 Database\nWhen you convert a Microsoft Dynamics NAV 2018 database to a Business Central version, you will receive compilation errors in several standard Dynamics NAV objects. This article describes how to resolve these errors.\n## Compilation Errors\nThe following table lists the compilation errors that might occur when you compile objects during the database conversion.\nObject Type|Object ID|Object Name|Function/Trigger|Error Message|Solution\nTable|5330|CRM Connection Setup|CreateOrganizationService|You have specified an unknown variable. CrmServiceClient Define the variable under 'Global C/AL symbols'.|If the application integrates with Dynamics 365 Sales, then to resolve this error, you must perform a full upgrade (application code and data). See Important Information and Considerations for Before Upgrading<upgrade-considerations#CRM>. If not integrating with Dynamics 365 Sales, you can ignore this error.\nTable|8620|Config. Tmpl. Selection Rules|OnValidate|Type conversion is not possible because 1 of the operators contains an invalid type. Integer := Text|Resolving Table 8620 Compilation Error<resolve-table-8620-error-converting-database>\nCodeunit|700|Page Management|VerifyPageID|Type conversion is not possible because 1 of the operators contains an invalid type. Text = Integer|Resolving Codeunit 700 Compilation Error<resolve-cu-700-error-converting-database>\nCodeunit|5330|CRM Integration Management|ImportCRMSolution|You have specified an unknown variable. ServiceManagement Define the variable under 'Global C/AL symbols'.|If the application integrates with Dynamics 365 Sales, then to resolve this error, you must perform a full upgrade (application code and data). See Important Information and Considerations for Before Upgrading<upgrade-considerations#CRM>. If not integrating with Dynamics 365 Sales, you can ignore this error.\nCodeunit|9010|Azure AD User Management|CreateNewUsersFromAzureAD|You have specified an unknown variable. GetUsersPage Define the variable under 'Global C/AL symbols'.|Resolving Codeunit 9010 Compilation Error<resolve-cu-9010-error-converting-database>.\nPage|2500|Extension Management|OnAction|There is no overload for method 'GenerateDesignerPackageZipStream' that takes '2' arguments.|Resolving Page 2500 Compilation Error<resolve-page-2500-error-converting-database>\nPage|6400|Flow Selector|FlowAddin::ControlAddInReady|When the function is called, the minimum number of parameters should be used. For example: MyFunc( .. , .. , .. )|Resolving Page 6400 and 6410 Compilation Errors<resolve-page-6400-6401-error-converting-database>.\nPage|6401|Flow Template Selector|FlowAddin::ControlAddInReady|When the function is called, the minimum number of parameters should be used. For example: MyFunc( .. , .. , .. )|Resolving Page 6400 and 6410 Compilation Errors<resolve-page-6400-6401-error-converting-database>.\nPage|9624|Finish Design List Part|GetTaskDisplayName|You have specified an unknown variable. Display Name Define the variable under 'Global C/AL symbols'.|See Resolving Page 9624 Compilation Error<resolve-page-9624-error-converting-database>.\nTable|1670|Option Lookup Buffer|FillBufferInternal|'SETPERMISSIONFILTER' is obsolete for Microsoft Dynamics NAV Server.|This warning and can be ignored.\nCodeunit|1751|Data Classification Eval. Data|ClassifySession|The 'Record2000000009' type is obsolete.|This warning and can be ignored or to clear it, remove the procedure `LOCAL PROCEDURE ClassifySession@72();` and the reference to it."}