{"id":17925,"date":"2018-06-06T11:45:12","date_gmt":"2018-06-06T09:45:12","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/nav\/?p=17925"},"modified":"2023-05-31T15:27:07","modified_gmt":"2023-05-31T22:27:07","slug":"navapplicationareahelper","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/it-professional\/2018\/06\/06\/navapplicationareahelper\/","title":{"rendered":"Change multiple Application Area tags with PowerShell"},"content":{"rendered":"

Visibility of the controls in Business Central can be\u00a0regulated by the ApplicationArea property. For more information, see (https:\/\/docs.microsoft.com\/en-us\/dynamics-nav\/applicationarea-property<\/a>).<\/p>\n

Before you\u00a0convert an\u00a0existing Dynamics NAV solution\u00a0to an extension written in AL, the ApplicationArea property must be set on all your\u00a0custom controls. Otherwise, they will not be visible.<\/p>\n

Setting\u00a0the ApplicationArea property one by one is a tedious task that can be partially automated with the following PowerShell scripts:<\/p>\n