View a BOM

The BOM tab displays the Bill of Materials for an assembly, read from .gitm/bom/<assembly>.json. GitMCloud only displays BOMs — generating them requires SolidWorks and the GitM add-in.

Prerequisites

• Signed in and connected.
• A BOM has been generated and checked in from GitM. See Generate a BOM on the GitM side.

See a BOM

1. Open the BOM tab.
2. If the repository has several assemblies, choose one from the assembly dropdown (fixed width; the .SLDASM extension is stripped for display — hover for the full name).
3. Toggle between List (≣) and Tree (⊟) views using the icon buttons.
4. To sort the flat list, click Sort ▼ and pick: Line # (default), Part No, Component, Qty, or Mass. Sort applies to List view only; Tree stays hierarchical.
5. To export, click ⋯ → Export to CSV.

Part numbers in the BOM

BOM lines are enriched with part numbers from .gitm/partnumbers.json using a fallback chain (exact path+config → path-only → unambiguous filename). A line may show no number if one was never allocated.

Expected result

• The BOM matches what GitM generated and checked in, with part numbers filled in where the registry has them.

Troubleshooting

Symptom	Cause	Fix
BOM tab is empty	No BOM generated/checked in, or no assembly selected.	Generate and check in from GitM; pick an assembly.
BOM looks out of date	The generating user generated but didn't check in.	They must check in the BOM change in GitM.
Part numbers missing on lines	Not yet allocated, or a path/config mismatch.	Allocate numbers; see Allocate a part number.
Columns look wrong	BOM JSON schema mismatch between GitM and GitMCloud versions.	Confirm both sides are on compatible versions.

Known limitations

• GitMCloud never writes BOM files. Generation is SolidWorks-only.
• The BOM schema (BomDocument / BomLine) is a shared contract with GitM; a schema change on the GitM side can break the display until GitMCloud is updated to match.