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. Each module card shows the publisher, name, version and target, with a badge for its role, e.g. EXT or APP. Click a module to highlight the module and its dependencies, and to show its details in the module details panel. Use the zoom buttons to zoom in and out, or to fit the graph to the view.
2	Details	Shows or hides the module details panel, with the metadata of the selected module.
3	Filter	Which dependencies and modules appear in the graph: Unresolved dependencies: include dependencies whose target module could not be resolved. Propagated dependencies: include implicit, propagated dependencies. For example, the dependency from VAT Group Management to Base Application is propagated via Application. System dependencies: include the System module and all dependencies to it. (Basically all modules except those without `platform` element.) Unused discoveries: also show discovered packages with a matching module ID that were not used, for example because the version is too low, the resolution mode excludes them, another package was resolved instead, or an earlier resolution step is selected. Test modules: include test modules and their dependencies.
4	Show	Optional information on the graph: each module's in-degree and out-degree, its location in the file system, and the version constraint on each dependency. Uncheck Custom node cards to draw modules as plain text labels.
5	Layout	The layout algorithm, edge routing and layer direction, and the relational emphasis: whether the inbound and/or outbound dependencies of the selected module are highlighted. Experiment with the options to find the layout that fits your purpose best.
6	Resolution step	Mostly for debugging purposes.
7	Save	Save the graph to a file.

Module graph page

We use cookies