Reference manual

Objects page

Loading window

The Loading window shows how far Prism has come with opening a workspace, and says why when the workspace cannot be opened. Package resolution is influenced by Package resolution options.

Opening it

Prism opens it whenever it opens a workspace: from the open buttons or the recent list on the Home page, from File › Open, and after Open from BC window has downloaded the symbol files. Press F1 in it to open this page.

Workspace foldersapp.json, *.al Package files*.app, in .alpackagesor al.packageCachePath Package cacheWhen Search packagecache is on Discovering modulesEach app.json, and theNavxManifest.xml insideeach .app Resolving dependenciesBy version; Search depthdecides how far Extracting packagesNew ones, into thepackage cache Loading symbols.al files where a module hassource; SymbolReference.jsonwhere it has none Indexing symbolsMembers and objectdependencies Code graphProcedural or Full, whenAuto-build graph is on Workspace foldersapp.json, *.al Package files*.app, .alpackages Discovering modulesEach app.json, and the NavxManifest.xmlinside each .app Resolving dependenciesBy version; Search depthdecides how far Package cacheWhen searched Extracting packagesNew ones, into the package cache Loading symbols.al files where a module has source,SymbolReference.json where it has none Indexing symbolsMembers and object dependencies Code graphProcedural or Full, when Auto-build graph is on
What Prism reads when it loads a workspace, in order, from the files to the index and the code graph.
Prism for AL loading a workspace
1 2 3 4 5
Loading a workspace.
# Name Description
1 Workspace The path of the workspace folder or file, with its last part at full strength. The title above it reads Opening and the workspace's name: the name of the .code-workspace file, or of the folder. Without a name, it reads Opening workspace….
2 Current activities Which of the two steps Prism is on and what it is doing, such as Step 1 of 2 · Extracting packages... 12 of 40. Step 1 starts (Initializing...), discovers the modules (Discovering modules), extracts the packages (Extracting packages) and resolves the dependencies (Resolving dependencies..., then Resolved N modules). Step 2 reads and indexes the symbols (Loading and indexing symbols..., or Indexing symbols... once every file is read), then resolves module topology, module scopes, object usages and object topology, and ends with Symbol indexing completed.... While Prism builds the workspace window, it shows Preparing view data..., Initializing window... and Showing workspace....
3 Overall progress Fills as the workspace loads: step 1 takes the first 30 percent and step 2 the rest, and a notch marks where step 2 starts. Once the symbols are indexed, it runs without a value while Prism prepares the window.
4 Timer Blank for the first two seconds. While Prism indexes the symbols, it shows the time left once it can estimate it, such as ~12s left; otherwise the time spent loading, such as Elapsed 4s.
5 Cancel Stops loading; the workspace does not open. It reads Canceling until Prism has stopped. Closing the window does the same.

When a workspace cannot be opened

The title reads Could not open and the workspace's name, the progress bar and the timer go, and the window lists why. Select Ok to close it; the workspace does not open.

When no version of a package satisfies every module that requires it, the window explains it in four parts:

PartWhat it shows
Requirement that broke Which module required what of which other module, and why no version fits, such as “Analytics requires Core ≥ 2.0.0.0, but the workspace has Core 1.0.0.0.”
Chain How Prism got there: the workspace's own module first, then each module it required, with the version required of it. The last link, in red, is the one that broke, with the version the workspace has.
Competing requirements The other requirements on the same module, each with the modules it came through (Required through), so you can see which one wins.
What to do What to change: raise or lower a version in an app.json, use a package built against the version the workspace has, download symbols, or add packages that agree on a version to a package folder. Which of these Prism suggests depends on whether the modules involved are in the workspace or are packages.

Other reasons a workspace cannot be opened are listed in red:

  • Error: dependency version conflict, with the module and the conflict.
  • Error: The same module identifier appears in two modules, with the module ID and the files.
  • Error: The workspace is empty.
  • Error: The workspace has no usable modules.
  • Exception, for an unexpected error: its Message, HRESULT, Help Link, Source and Stack Trace. Send it to us with the Feedback window.

A nested project, an app.json inside a workspace folder, is listed with Error or Warning, its Path, which you can select to show it in File Explorer, and a Detail that says what it means. See Unresolved modules for modules Prism cannot find.

An unhandled error has occurred. Reload 🗙