Discovery page
The Discovery page of the Workspace window lists every
app.json file and Package file Prism for AL
considered while loading the workspace: which it included, which it ignored, and which failed and why.
Opening it
Select Discovery in the rail of the workspace window. On a module's Discovery tab of the Solution page, double-click a file, or select its link, to open this page with that file selected.
| # | Name | Description |
|---|---|---|
| 1 | Search |
Type to filter the table on path, status, signature or module
metadata (publisher, name, version and id). A version range such as 1.0..2.0
matches module versions. The text beside the field shows how many files are listed, such as 12 of 40 discoveries.
|
| 2 | Status |
One of the following:
|
| 3 | Path |
The path of the app.json or .app file, within the workspace.
Paths of ignored packages are dimmed.
|
| 4 | Signature |
A Prism-generated signature of the package file, shown as a short hash. An
app.json file has no signature.
|
| 5 | app.json file |
The root of a Visual Studio Code project, here the LearnPrism
folder of the workspace. Projects are listed before packages.
Select the row to see its details.
|
| 6 | .app file included |
A package included in the workspace. Select the row to see its details. |
| 7 | .app file ignored |
A package that was ignored, typically because another version of the module is used, because there are no dependencies to it, or because dependencies are ignored due to the selected item of the Search depth. Select the row to see its details. |
| 8 | Module details | Details of the selected row. The Discovery expander shows the path of the file; select it to reveal the file in File Explorer. The Core, Environment, Code and Miscellaneous expanders show the module's metadata. Expand them for the details. |
Files with errors
When a file has failed, the table gets an Error column with the error, and the Discovery expander of the details shows it as the file's Status. A package in a runtime format, for example, reads “Runtime package format not supported.”; see Packages ignored when opening folder.
When modules cannot be resolved, a note above the table reads “Ensure the requisite symbols (packages) have all been downloaded and do not have any errors.”, with a link to Microsoft's documentation on runtime packages. The Modules tab lists the unresolved modules.
Related
- Diagnostics page: unresolved modules and other loading issues.
- Packages ignored when opening folder: why a package is missing after loading.
- Solution page: each module's own discovery files.