Reference manual

Module graph page

This page is hosted by the Workspace window.

The module graph visualizes all module dependencies of the current workspace. All information is deduced from app.json/ NavxManifest.xml metadata files. Depending on settings, the graph includes all kinds of Module dependencies:

Prism for AL module dependency graph
Module dependency graph.
# Name Description
1 Graph Modules are nodes and dependencies are edges in the graph. Click a module to high-light the module and it's outgoing dependencies and its module details on the right. Use FN and MOUSE WHEEL to zoom in and out.
2 Module details Module details from the metadata file.
3 Layout algorithm The algorithm used to layout the graph. Experiment with the options to find the one that fit's your purpose best.
4 Routing Edge routing algorithm.
5 Direction The direction of the layout.
6 Emphasis For a selected item, which connected dependencies are highlighted: In, out or both?
5 In-degree/out-degree Check this to annotate modules with the total number of in- and out-going dependencies.
8 Location Check this to annotate modules with location of the module in the file system.
9 Version constraint Check this to annotate dependencies with the version constraint specified.
10 Unused Check this to only show modules that are referenced by another module.
11 Unresolved Check this to include unresolved dependencies.
12 Propagated Check this to include propagated dependencies. In the example above, the dependency from VAT Group Management to Base Application is propagated via Application.
13 System Check this to include System module and all dependencies to it. (Basically all modules except those without platform element.)
14 Resolution step Mostly for debugging purposes.