Home page
This page is hosted by the Main window.

| # | Name | Description |
|---|---|---|
| 1 | Open workspace file |
Opens a workspace based on
Visual Studio Code Once the file has been selected, the Loading window opens. |
| 2 | Open from BC | Opens a solution from a running Business Central service. Enter the connection details of the service and a download folder. Prism for AL downloads the solution's symbol packages into the folder and opens it as a workspace, and the Loading window opens. |
| 3 | Open folder |
The simplest usage of Open folder is to open a
Visual Studio Code project folder, i.e. a
file system folder containing an
Prism for AL can also open a folder that has sub folders (recursively) that are
Visual Studio Code projects such as this:
├───app-A │ │ app.json │ │ DoThis.Codeunit.al │ │ │ └───.alpackages └───app-B │ app.json │ DoThat.Codeunit.al │ └───.alpackagesThis works similar to opening a workspace file.
Another option is to open a folder which contains packages ( Once the folder has been selected, the Loading window opens. |
| 4 | Open package | Opens a package file (*.app). This will create an in-memory artificial module with a dependency to the single package. Package dependencies are not included; to achieve that, use Open folder instead. Once the file has been selected, the Loading window opens. |
| 5 | Auto-build graph | Determines whether a Code graph is automatically built when a workspace is opened. |
| 6 | Package resolution options |
The following options control how packages are resolved during
workspace loading:
|
| 7 | Graph detail | Determines whether a more compact Procedural flow graph (Procedural) or a Full graph (Full) is loaded. A procedural graph has inter-procedural calls only, so it is smaller and faster to load. A full graph adds expression- and statement-level flows, and is slower to load. |
| 8 | Recent workspaces | This is a list of workspaces you have opened recently, newest first, grouped by when you opened them. Click a recent workspace or use shortcuts Ctrl + 1, Ctrl + 2 etc. (counting from the top) to open the workspace. If the workspace is already open, focus shifts to the workspace window. The Search recent box above the list filters it by name, path or service URL. Right-click a recent workspace to open it, reveal it in File Explorer, or remove it or all recent items from the list. For a workspace opened from Business Central, the menu can also re-download its symbols and open Business Central. |
| 9 | License | The license part shows the current license (if any is installed) and its status. The tooltip on the status gives additional information, e.g. expiration date when the license is valid. Without a license, Prism for AL is feature-limited. Subscribe or Get a trial license to enable all features. Click the Activate new license button to open the License key window. Without a valid license, or when a trial license has expired, a Get trial license key link below it opens the Trial license window. |
| 10 | Features summary | The features part shows a summary of your usages of main Prism for AL features: how many you have explored, and how many are left. The percentage complete indicates the percentage of Prism for AL's main features that you have used. Click the features button in the main window to navigate to the Features page. After an update, the summary also counts the features that are new or updated in the release, and the Release notes link opens the release notes in your default browser. |
| 11 | Status | Watch this for status messages like availability of new releases of Prism for AL. Click the status to open your default browser on the download page for Prism for AL. The button to its left opens the release notes. |
The options (5 to 7) apply when you open a workspace, including one of the Recent workspaces. They start from the defaults in the Settings page, and a change made here lasts until Prism restarts or the settings are saved.
Memcache is a setting in the Settings page.
When it is enabled (default), Prism for AL snapshots the source files found in workspace folders
(but not source code found in .app files) during loading.
This insulates the viewing experience from file changes by an external editor
like Visual Studio Code.
However, it also increases memory usage. You can
monitor usage
in the
Workspace window.
Search depth values (dotted lines in the pictographs are propagated dependencies):
| Mnemonic | Description | Pictograph |
|---|---|---|
| W | Workspace: Workspace modules ( app.json), only. No packages are included.
|
![]() |
| W→P | Workspace and direct dependencies: Workspace modules ( app.json) as well as direct package dependencies (*.app)
|
![]() |
| W→PP | Workspace and direct/propagated dependencies: Workspace modules ( app.json) as well as direct package dependencies (*.app) and their propagated dependencies.
|
![]() |
| W→P→* | Workspace and transitive dependencies: Workspace modules (app.json) and all dependencies transitively (recursively). Notice that this setting may lead to unexpected results as old, now unused packages in Visual Studio Code .alpackages folders may be included.
|
![]() |



