Troubleshooting

This guide covers common issues with grid views: the SysMLv2 Views panel, table and matrix content, editing, and the SysideViews library. Grid views surface problems in the SysMLv2 Views panel when no view can be shown at all, and in banners inside an open view.

For issues not specific to grid views, such as installation, licensing, or a hidden panel, see the general Troubleshooting guide. It also explains what to include in a support report.

Panel issues

The panel shows no views

If the panel shows Views are unavailable because the Modeler server is not running, the language server is starting or has crashed:

  1. Wait a moment, then use the Retry button

  2. If the problem persists, check the Syside output channel for errors

If the panel shows No views found in the model, no view usage in the workspace is typed by a SysideViews view definition:

  1. If the message offers Add SysideViews.sysml or Update SysideViews.sysml, accept the offer; the library file is missing or out of date

  2. Re-check the view definitions against Configure table views or Configure matrix views

“Views are disabled due to model issues”

Any diagnostic in the model disables all grid views and editing, including warnings. This is deliberate: writing through a view into a model that does not resolve cleanly could corrupt it.

  1. Read the list under the panel message; clicking an entry opens the offending location

  2. Fix every listed error and warning; the views re-enable automatically

View content issues

A table or matrix is empty

  1. Check the expose scope for typos. A qualified name that resolves to nothing produces an empty view, not an error.

  2. Check the default exclusions: reference and abstract elements are excluded until the corresponding ContentView flag is set, and standard-library elements are always excluded.

  3. If the missing definitions are only reachable through usages or through the heritage chain, set exposeFeaturesAndHeritage.

  4. For matrices, read the per-axis warnings, such as Matrix has no rows. Check the rowView’s `expose` and `filter` clauses. Each axis is an independent selection, so fix the named sub-view.

A matrix opened as read-only

  1. Read the warning banner; it names the cause.

  2. If the cellView filter admits more than one relationship kind, narrow it to a single kind: use one of the editable presets (ConnectionMatrixView, AllocationMatrixView, RequirementMatrixView), or add a filter clause that excludes the unintended kinds.

  3. If the cellView filter admits none of the supported kinds, admit one of the recognised predicates: allocation (hastype SysML::AllocationUsage), connection (hastype SysML::ConnectionUsage), or derivation (@ RequirementDerivation::derivation).

  4. If the banner says the view must expose exactly one Type from its cellView, point the cellView expose at the single container Type that owns the relationship usages (see Supported modelling pattern).

  5. If the model has diagnostics, see “Views are disabled due to model issues”.

A column shows an error, not values

Column `…`: … in a banner above the table means the column’s navigation chain is invalid; the message names the offending step and the rule it broke. The column degrades to empty read-only cells, and the rest of the view keeps working.

  1. Find the named column view in the SysML source

  2. Apply the remedy in the message; Navigation chains covers what a chain may contain

Representation parameters never produce this banner: a languageName that matches no textual body degrades the column to its read-only defaultValue cells instead.

The whole table is disabled

`…` and `…` fan out in parallel, but a table’s fan-outs must form a single chain. Two anchors fan out in parallel. Rows are a property of the table as a whole, so this is the one chain error that disables the whole table instead of degrading a single column.

  1. Follow the remedy in the message: reuse one anchor for both columns, or chain the second anchor through the first

A hierarchical table reports no single root

HierarchicalTableView “…” must expose exactly one Definition; got N. The tree hangs off a single root definition, which itself is not a row (see Hierarchical table views).

  1. If N is 0, check the expose scope and the default exclusions, as for an empty view

  2. If N is more than one, narrow the expose / filter clauses until exactly one definition survives

Editing issues

Creating or editing is disabled

  1. If Add Traceability is disabled for a row or column, the axis Definition has no usage in the cell container, or more than one. See Disabled cells.

  2. If editing is disabled for some rows of a hierarchical table, the definition appears more than once in the hierarchy, so a write would be ambiguous. See the Definition-Usage pattern.

  3. If Add Requirement is greyed out, the view’s filter clauses do not admit requirement elements, or the model cannot currently be written to: it has diagnostics, source files hold unsaved edits, or another write is still in flight. See Create requirements.

Warnings about relationships

  • N cell(s) represent multiple traceability connections… More than one relationship exists between the same pair of elements, and the warning details list each one. This is informational, not an error.

  • N derivation connection(s) have non-Requirement endpoint(s)… A derivation relationship connects elements that are not RequirementUsage or RequirementDefinition. Fix the relationship endpoints in the model.

Library issues

“Workspace SysideViews.sysml is out of date”

The workspace copy of the library is older than the one bundled with the extension.

  1. Click Overwrite with bundled version in the banner, or run Update SysideViews.sysml from bundled copy from the command palette

  2. Avoid editing SysideViews.sysml by hand; updating replaces the file