Unresolved modules
Symptom: the Diagnostics expander on the Solution page lists Unresolved modules you did not expect.
| # | Name | Description |
|---|---|---|
| 1 | Unresolved modules | The number of modules the workspace depends on but Prism for AL did not find. Select the link to open the Diagnostics page. |
| 2 | Runtime package warning | Shown when the workspace also has runtime packages, which Prism for AL cannot read. See Packages ignored when opening folder. |
Cause: a module named in an app.json dependency is not in the workspace or its
package folders. Select Unresolved modules, then select each row on the
Modules tab of the Diagnostics page. Its Status names the cause:
- “Module not found in workspace”: no folder or package in the workspace provides the module.
- “Download symbols from server and reload workspace”: the module belongs to the workspace, but its symbols have not been downloaded.
Fix:
- In Visual Studio Code, run AL: Download symbols for the workspace.
- Select the Reload button in the Workspace window to load the workspace again.
-
If modules are still unresolved, record the workspace with Help › Troubleshoot › Record Workspace…
in the Control Panel (see the
Troubleshoot menu item) and email us the
.wrecfile. We use it to reproduce the problem.