Metra first uses predictable table and header detection. Review the proposed sheet or PDF table, its confidence explanation and the representative source rows. Select only regions containing equipment.
Map each useful source column to one Metra field. At least one column must map to Equipment · Internal asset ID. Ignore report-only columns. Clients map to Metra Customer records; sites and locations remain separate organisation-owned records rather than equipment text fields.
Choose whether missing clients, sites or locations may be created. Existing structure is reused only through exact organisation-scoped matching; Metra does not silently fuzzy-merge similar names. Save the mapping, then select Validate and preview.
No records are created until an authorised user approves the validation snapshot and runs the atomic import.
Returning to an import restores its saved mapping and latest valid preview. Suggested mappings do not replace saved choices. Review the snapshot and confirm it again before selecting Confirm and run import; confirmation is not carried across visits. Members without execution permission can review the preview and hand the same import page to an owner or authorised importer. A queued or completed run opens its existing results instead of creating another run. If a queue response is lost, retrying from the same page reuses that request's identity.
Next: Resolve import errors and confirm.
Resolve categories per row
Map a source column to Equipment · Category when each row names its category. Metra resolves an active category by its organisation-scoped ID or name. Select Fallback equipment category only for rows with a blank category; a nonblank unrecognised or foreign category remains a preview error even when a fallback is selected.
The chosen site and location become the initial equipment placement when the import commits. The equipment and placement are saved together; invalid placement or audit failure does not leave a partial equipment record.
Recover a version conflict
AI analysis, mapping saves and validation use the committed import version. A real edit from another window can still conflict. Metra keeps your entered mapping choices. Select Refresh version and keep mapping, review the retained choices, then save explicitly if they should replace the other mapping. This does not retry or overwrite automatically.
To abandon an unfinished import, select Discard unfinished import, then Confirm discard. Its source, mapping and history remain retained. Start a new import to continue; completed or running imports cannot be discarded through this action.
Map permanent equipment ownership
Use Equipment · Permanent ownership type (unknown, organisation or client) and Equipment · Owner client (existing ID, name or reference) for explicit ownership. A client owner must resolve uniquely to an active existing client in this organisation. The import does not invent clients or infer permanent ownership from a movable site. Review unresolved or ambiguous owner mappings before committing. Placement and custody retain their separate mappings and history.
Validation retains the chosen client's identity. Renaming that client or reusing its old name or reference for another client does not transfer ownership in an approved preview. If the retained client is archived or unavailable, review the mapping and select Validate and preview again. Older previews that contain owner clients also need validation again before execution so that Metra can retain the intended identity.