Open from BC
Symptom: You get an error notification while connecting to or downloading from Business Central.
A number of things can go wrong when you open a solution from a running Business Central instance.
Prism for AL pretty much mimics the AL: Download symbols command in Visual Studio Code,
so if somethings goes wrong, the first thing to check is that you can download symbols from Visual Studio Code.
In order to download all apps, Prism for AL retrieves a list of published apps. Therefore, the connecting user needs to
have a permission set that includes read permission to TableData of Published Application.
Here follows a list of typical issues grouped by notification (or browser) message:
Entra ID sign-in
On-premises connection errors
Online connection errors
Download failed
Configuration
To check the OData services configuration on the server:
Use an administrator Business Central Administration Shell (or any powershell with
the NavAdminTools module imported)
to issue the following command (replace <BC> with instance name):
(Get-NAVServerConfiguration <BC>) | Where-Object { $_.Key -match "ODataServices(Enabled|Port|SSLEnabled)" }To check the Developer services configuration on the server:
Use an administrator Business Central Administration Shell (or any powershell with
the NavAdminTools module imported)
to issue the following command (replace <BC> with instance name):
(Get-NAVServerConfiguration <BC>) | Where-Object { $_.Key -match "DeveloperServices(Enabled|Port|SSLEnabled)" }To check if the APIV2 app is installed on the server:
Use an administrator Business Central Administration Shell (or any powershell with
the NavAdminTools module imported)
to issue the following command (replace <BC> with instance name, and on
multitenant installations default with the requested tenant):
Get-NAVAppInfo -ServerInstance <BC> -Tenant default | Where-object { $_.Name -eq "_Exclude_APIV2_" }If the app is installed, information about the app is returned. Otherwise, no information is returned.