Edit in Excel

Edit in Excel (/edit-in-excel) lets you round-trip a subset of a weld’s fields through Excel instead of editing them one at a time in the weld matrix. It’s a batch return, not offline sync — every change still goes through the same audited rules as the app.

Before you start

You need Weld Associate access or higher, plus write access to the project — a lower role can open the screen but is refused when it tries to check out or return a workbook.

Check out

1. Open Edit in Excel from the navigation.
2. Select Check out for editing. This downloads an Excel workbook of the whole project’s active welds, with a hidden, per-row identity token — you never see or edit it.

Only a whole-project check-out is available today; there’s no per-ISO scope picker yet.

Edit the workbook

Only five columns are editable: Weld Date, Schedule, Spool, Joint Location, and Description. Everything else on the sheet — ISO drawing, weld number, weld type, latest RT, and status — is shown for context only and is ignored on return, even if you change it.

A blank cell means “leave unchanged,” not “clear”

Leaving an editable cell blank never clears the field — it’s read as “no change.” To remove a weld entirely, use the Archive column instead (below). This protects a whole-project workbook from an accidental Excel deletion silently wiping data.

Write Weld Date as yyyy-mm-dd — for example 2026-05-07 — which is the form the check-out writes. A slash-separated date is read month-first, so 05/07/2026 means 7 May, not 5 July. A date MaxTrax can’t read at all doesn’t quietly disappear: the whole row is rejected on return, with the offending text shown in the reason, so you can fix it and return the file again.

To remove a weld, type TRUE in its Archive column. A row with no hidden identity token (a row you added yourself) can’t be archived — remove the flag, or archive the row that actually owns that weld.

You can also append new rows: a row with no identity token, but with a drawing number, weld label, and weld-type code that match something already in the project, creates a new weld — as a skeleton only. Give it its full descriptive detail on your next check-out and return, or use Import for full new-weld authoring in one pass.

Return the workbook

1. Select Return workbook and choose the file you checked out — it must be the same file; a plain grid or report export has no round-trip marker and is refused outright, with nothing applied.
2. Review the counts under Review what will change — updates, creates, archives, and any conflicts or rejections — before anything is written.
3. If any rows show a version conflict (someone changed that weld on the server since you checked it out), choose Keep mine or Keep theirs for each one. Nothing is overwritten automatically.
4. Select Confirm and apply.

What happens next

Each row applies as its own audited update, create, or archive, exactly as if you’d made the change in the app — the same guards apply (a signed ISO still blocks a change, for example). A summary shows how many rows were updated, created, archived, held for an unresolved conflict, or rejected, with the reason for each rejected or held row.

Note

The Runs & history tab on this page currently lists ordinary Excel imports, not Edit-in-Excel returns — a returned workbook doesn’t yet get its own entry there. Each applied row still carries full audit history on the weld itself.

Related

• Import weld data from Excel — full new-weld, ISO, and inspection authoring; the place to go when Edit in Excel’s fixed field set isn’t enough.
• The weld matrix — editing one weld at a time.
• Weld status lifecycle — what a signed ISO locks.