Resolving Compilation Errors When Converting a Dynamics NAV 2017 Database
When you convert a Microsoft Dynamics NAV 2017 database to a newer Dynamics NAV version, you will receive compilation errors in several standard Dynamics NAV objects. This article describes how to resolve these errors.
Compilation Errors
The following table lists the compilation errors that might occur when you compile objects during the database conversion.
| Object Type | Object ID | Object Name | Function/Trigger | Error Message | Solution |
|---|---|---|---|---|---|
| Codeunit | 700 | Page Management | CheckAnyRoleAssignedToUser | Type conversion is not possible because 1 of the operators contains an invalid type. Text = Integer. | See Resolving Codeunit 700 Page Management Compilation Error. |
| Codeunit | 5330 | CRM Integration Management | CheckAnyRoleAssignedToUser | You have specified an unknown variable. Entities Define the variable under 'Global C/AL symbols'. | See Resolving Codeunit 5330 CRM Integration Management Compilation Error. |
| Codeunit | 6303 | Azure AD Auth Flow | Initialize | Type conversion is not possible because 1 of the operators contains an invalid type. DotNet := GUID | See Resolving Codeunit 6303 Azure AD Auth Flow Compilation Error. |
| Page | 9621 | Add Page Fields | SaveNewFieldDefinition | Type conversion is not possible because 1 of the operators contains an invalid type. Integer := OemMText | See Resolving Page 9621 Add Page Fields Compilation Error. |
| Page | 9626 | New Page Patterns List Part | - | TableData 2000000174 does not exist. | Resolving Page 9626 New Page Patterns List Part Compilation Error. |