Import and Export
Use the header Export menu to save the current chain in several formats or load a previously exported JSON chain.
Diagram export
Use these options when you want an image of the canvas:
| Format | Use case |
|---|---|
| PNG | Screenshots, slides, documentation |
| Print-ready chain diagram |
These exports include only the chain canvas. Interactive controls such as buttons and handles are hidden automatically.
Data export
The same menu also provides structured exports for reuse outside the canvas:
| Format | Contents | Typical use |
|---|---|---|
| JSON | Full chain structure in importable form: ordered blocks, roles, labels, linked MPNs, numeric parameters, tags, and connections | Save, share, duplicate, or migrate a chain |
| CSV | One row per block with canonical parameter columns | Spreadsheet review or editing |
| BOM CSV | Linked component and bill-of-materials-oriented data | Parts review or procurement workflows |
| Analysis CSV | Current computed analysis results | Offline reporting or comparisons |
Import JSON
Use Export > Import JSON to load a clean JSON chain file.
The import file must contain:
nodesedges
Optional top-level metadata may also be present:
format_versionexported_at
Each node can include:
blockcomponentlabelmpnparamstags
Each edge can include:
from_blockto_blocksrc_portdst_port
Import behavior
Import rebuilds the chain from the JSON payload in a deterministic order:
- The current chain is reset.
- Blocks are recreated in block order.
- Connections are restored.
- Numeric parameters are applied.
- Tags are applied.
Import replaces the current chain contents. Save a Snapshot first if you may want to return to the current state.
Parameter handling
JSON import accepts numeric block parameters only.
Parameter keys are matched flexibly against the block parameter registry. For example, import can resolve canonical IDs such as gain_db as well as label-style keys such as Gain (dB) when they map unambiguously to a block parameter.
Unknown parameter keys are ignored. Invalid non-numeric parameter values cause the import to fail.
Notes
- JSON export is intended to round-trip with JSON import.
- CSV export is for review convenience and is not the same as the JSON import format.
- BOM CSV and Analysis CSV depend on the data currently available in the UI.