Solution page

This page is hosted by the Workspace window.

Use the solution page to get an overview of what the solution consists of.

You can make this page the first page that opens when Prism has loaded a workspace; see Settings page.

The initial view shows all modules and the total object count per object type:

Prism for AL: solution overview — Solution overview (no module selected).

If you see a column indicating errors in the above table, please refer to the Parse errors.

#	Name	Description
1	Search	Searches the publisher, name, version and module id. A version range such as `1.0..2.0` (or `1.0..` or `..2.0`) keeps the modules whose version lies in the range; add text to the range to match both.
2	Topologic order (#)	The Topological order deduced from the module dependencies.
3	Publisher	The publisher name from the manifest.
4	Name	The name of the module.
5	Version	The version of the module.
6	Constraint	The aggregated version constraint by other modules of the workspace.
7	Role	The kind of module: PLATFORM, SYSTEM (System and System Application), BASE (Base Application), APP (Application), TEST or EXT (an extension). Hover over a chip for its description.
8	Origin	Indicates whether the module is from a workspace folder or from a package.
9	Total object count	Total number of objects found in the solution.
10	Object count per object type	Number of objects per type.
11	Export solution metrics	Exports solution metrics to Excel. These metrics can be useful when estimating the 'size' of a customer solution.
12	Explore file system	Opens the File explorer window, which shows a tree view that presents the virtual file system which Prism for AL uses for this the solution. The file system includes files from your workspace folder(s) and packages (`.app` files).
13	Reveal workspace	Opens Windows Explorer and shows the directory or `.code-workspace` file that corresponds to the current workspace.
14	Reveal selected item	Scrolls the view, so the selected item is visible. Available when a module is selected.
15	AL Settings	Expand to see the AL settings cascaded from user and workspace configuration.

When the workspace has health issues, such as unresolved dependencies or files with errors, a Diagnostics expander above Object metrics lists them.

Click a module to view details in the right panel, which is a tabbed view.

Details tab

Details of the current, mostly from .app files, but also data from Prism's module resolution and object metrics.

Prism for AL: Module details — Module details.

#	Name	Description
1	Discovery	Metadata about the resolved module. To see which other versions Prism for AL considered during module resolution, use the Discovery tab described below.
2	Core, Environment, Code and Miscellaneous	Presents module data found in `app.json` files for workspace folders and `NavxManifest.xml` files for packaged modules (`.app` files).
3	Object metrics	Shows the count of object per object type for the selected module.
4	Module graph	Shows the Module graph page highlighting the currently selected module.
5	Collapse	Collapses all expanders.
6	Expand	Expands all expanders.
7	Close module view	Close the module view and revert to the module overview with no module selected.

Two more expanders appear only for some modules, so the screenshot does not show them. AL Settings appears for a module from a workspace folder and shows the AL settings cascaded from user, workspace and module configuration, marking which level overrides which; check Show all settings to include settings that are not set, and use the search field to filter them. Git shows the version control metadata of the module's repository, when the workspace spans more than one Git repository.

Discovery tab

The Module discovery tab list all Package files that Prism for AL has considered while loading and shows which module was chosen.

Prism for AL: Module discovery — Module discovery.

#	Name	Description
1	Go	Click the link symbol (or double-click the row) to show the Discovery page with the current module pre-selected.
2	Used	Indicates which candidate was chosen by the module resolution process.
3	Path	The virtual path to the `.app` file or workspace folder.

Usings tab

The Module usings tab list which other modules the currently selected module depends on. Each row represents a dependency on another module.

Prism for AL: Module usings — Module usings.

#	Name	Description
1	Go	Click the link symbol (or double-click the row) to select the module in the Solution view.
2	Publisher	The publisher of the dependency
3	Name	The module name of the dependency
4	Version	The version of the dependency.
5	Constraint	The version constraint the currently selected module has on the module of the dependency.
6	Status	If you see anything here, there is a module resolution error. Use the tooltip to help diagnose.
7	Kind	Indicates where the dependency comes from: Platform: The `platform` attribute in `app.json` Application: The `application` attribute in `app.json` Propagated: The dependency comes from a propagated dependency, typically via the dependency specified in the `application` attribute in `app.json` (empty): The dependency is a "normal" dependency specified in the `dependencies` attribute in `app.json`

Usages tab

The Module usages tab list which other modules depend on the currently selected module. Each row represents a dependency on the current module.

Prism for AL: Module usages — Module usages.

#	Name	Description
1	Go	Click the link symbol (or double-click the row) to select the depending module in the Solution view.
2	Publisher	The publisher of the depending module.
3	Name	The module name of the depending module.
4	Version	The version of the depending module.

Namespaces tab

The Module namespaces tab list the namespaces of objects of the currently selected module. Each row represents a namespace in this module.

Prism for AL: Module namespaces — Module namespaces.

#	Name	Description
1	Go	Click the link symbol (or double-click the row) to show the namespace in the Namespaces page.
2	Namespace	The full namespace name.

Translations tab

The Module translations tab lists all XLIFF files that translate something in the currently selected module. There is one row for each combination of XLIFF file, and source and target languages in the file.

Prism for AL: Module translations — Module translations.

#	Name	Description
1	Go	Click the icon (or double-click the row) to reveal the translation file in File Explorer. This works for XLIFF files defined in a workspace, only, not for XLIFF files found in `.app` files.
2	External	Indicates if this translation targets a different module.
3	Origin	Shows which module contains the XLIFF file. "Internal" means the currently selected module. Other values refer to module names of the owning module.
4	Source	The source language of the translation.
5	Target	The target language of the translation.
6	File	The name of the XLIFF source file.