Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
737
stars
243
forks
source link
Merge-NAVApplicationObject Update from NAV 2018 CU08 to Business Central failed - "ApplicationArea is not valid property for Page" #4095
Describe the bug
I tried to update our solution from NAV 2018 W1 CU08 to Business Central W1. I exported the obects as txt directly from the Development Environment.
More than 1000 objects failed with warning:
"ApplicationArea is not valid property for Page."
"ApplicationArea is not valid property for Report."
"AccessByPermission is not Valid property for Page."
"APIPublisher is not valid property for Page."
...
To Reproduce
I used the following PowerShell Script:
$BaseVersionPath = 'C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\130\RoleTailored Client\'
Short Update: If I export all objects from Business Central using PowerShell command Export-NAVApplicationObject the merge do not result in failed objects.
Describe the bug I tried to update our solution from NAV 2018 W1 CU08 to Business Central W1. I exported the obects as txt directly from the Development Environment.
More than 1000 objects failed with warning: "ApplicationArea is not valid property for Page." "ApplicationArea is not valid property for Report." "AccessByPermission is not Valid property for Page." "APIPublisher is not valid property for Page." ...
To Reproduce I used the following PowerShell Script:
$BaseVersionPath = 'C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\130\RoleTailored Client\'
$NAVAppsToolsDLL = $BaseVersionPath + 'Microsoft.Dynamics.Nav.Apps.Tools.dll' $NAVAppToolsPS = $BaseVersionPath + 'Microsoft.Dynamics.Nav.Apps.Tools.psd1' $NAVModelTools = $BaseVersionPath + 'Microsoft.Dynamics.Nav.Model.Tools.psd1' $NAVAppsManagementDLL = $BaseVersionPath + 'Microsoft.Dynamics.Nav.Apps.Management.dll' $NAVAppsManagementPS = $BaseVersionPath + 'Microsoft.Dynamics.Nav.Apps.Management.psd1'
Import-Module $NAVAppsToolsDLL -Force Import-Module $NAVAppToolsPS -Force Import-Module $NAVModelTools -Force Import-Module $NAVAppsManagementDLL -Force Import-Module $NAVAppsManagementPS -Force
Merge-NAVApplicationObject -OriginalPath 'C:\Objects 2018 CU08 W1' -ModifiedPath 'C:\Solution Objects 2018 CU08 W1' -TargetPath 'C:\Objects BC W1' -ResultPath 'C:\Result'
Expected behavior The properties in the pages and reports should not produce errors.
Screenshots
Versions: