Export data or a visualization

Export a table for analysis in another tool, or a visualization image for a presentation. Choose the scope before downloading: selected rows, the current page and all filtered results are different outputs.

Export assets to CSV or XLSX

1. Open the inventory or tabular view. Set the filters, search and sort order you want.
2. Select rows if you want only those assets, then choose Actions > Export CSV / XLSX.
3. Under Scope, choose Export selected assets, Export current page or Export all assets. Check the displayed count.
4. Choose Format: XLSX or CSV. The dialog starts with XLSX.
5. Set Headers to Label or Key, then choose Dates format: year-month-day or day-month-year, with hyphens.
6. Review columns and relationship representations: name, identifier or an available unique key. Inspect the preview.
7. Click Export to CSV or Export to XLSX. Accept the browser download prompt if it appears.
8. Open the saved file and check its rows, headers and values.

The default scope is all, even if you selected rows before opening the dialog. All means the results of the current filters, search and sort, not every asset in the organization.

Selected assets are reread by identifier and retain selection order. The current-page option uses loaded rows. The preview shows at most ten rows; it is not the final file's row count.

Choose useful columns

Hidden properties are not offered for export, and permissions filter the returned data. Identifier and name remain required columns. Other initial selections reflect the current view where applicable; adjust them in the dialog.

For relationships, decide whether the receiving tool needs related names, identifiers or unique keys. Names suit reading, while stable identifiers help reconcile records. An export is not automatically a ready-to-import file; follow file preparation before importing it again.

Rich-text values become Markdown. Single-choice values use their label, and multiple-choice values form a comma-separated list. CSV uses UTF-8 with a byte-order marker and comma separators. If your spreadsheet puts everything into one column, import the file explicitly with comma as the separator.

XLSX contains exported cell values. It does not reproduce all Boldo formatting or computed-property formulas as spreadsheet formulas.

Export relationships

Open the relationship inventory or view and its export dialog. Choose selected rows, the current page or all current results, then select format, headers, dates and columns before downloading.

The export preserves the relationship identifier and source/target names. You can include endpoint identifiers or unique keys and visible relationship properties. Creation date is selected by default; update date is optional.

Keep source and target columns distinct: they carry the direction of the relationship. Two relationships between the same assets can have different identities and property values. Check the identifiers when reconciling parallel relationships.

Export an image

1. Open the content in the intended context and wait for it to finish rendering.
2. For a diagram, chart or map, choose Actions > Export to image. For an impact analysis in graph view, choose Actions > Export > Image. For a process, open Flow editor, then choose Export to image in the page’s ⋮ menu.
3. For a diagram camera, use its export command in the cameras panel instead.
4. Accept the download if prompted, then open the saved PNG.

While the image is prepared, a message says the export is in progress; the page may freeze for a few seconds. Image exported then appears once the file is handed to the browser for download. If a diagram, chart, nested map or process is empty or still loading, a message says there is nothing to export. For an impact analysis, the Image item stays greyed out while it loads or when nothing is impacted. If the export fails, an error message appears: try again.

Content	Output and scope
Diagram	Export to image produces PNG for the global diagram. A camera export uses its frame.
Chart	PNG of the rendered chart, rather than its configuration or raw data.
Nested map	PNG through its export menu when the content can be exported.
Process	PNG of the flow, from the asset page.
Impact analysis	PNG of the graph, separately from table and path exports.
Dashboard	No general image-export command is available in its current menu. Export the relevant source visualization instead.

For a diagram, choose the camera frame when you want a specific composition. The global export includes node bounds, including camera nodes; it may contain more space than the current viewport. For the whole diagram, dimensions are proportionally reduced to at most 8,000 logical units per side before rasterization. The pixel ratio is applied afterwards: this is not an 8,000-pixel limit on the resulting PNG, nor a camera-export size rule. Check the resulting readability. Remote images that fail to load can be omitted, and image-loading waits are bounded. If detail is insufficient, export separate camera frames.

Check the downloaded image at its intended presentation size. Verify labels, cropping, colors and embedded images. Browser preparation or a success message does not by itself confirm that the file reached your downloads folder.

Export an impact analysis

The impact analysis offers separate table, path and graph outputs. Choose the output that answers your question. Under Actions > Export, choose CSV or XLSX for the table, Paths (CSV) / Paths (XLSX) for paths, or Image for the graph in graph view.

The table supports CSV and XLSX with names, types, distance and impact information such as path count, criticality or stopping conditions. When the analysis has several stages, it also includes a stage column. It does not include a dedicated asset-ID column. A path count prefixed by ≥ indicates truncation.

Path exports support CSV and XLSX and include source/target identifiers, steps and traversal directions. They contain the calculated paths retained by the analysis, not every theoretically possible path. Intermediate nodes may appear even when they are not rows in the impact table.

In scenario-aware table exports, the filename includes a scenario suffix and a scenario column identifies the context. This marker does not apply the scenario's changes to real data. Check the active context and the exported values before sharing the file.