Import weld data from Excel

This guide covers the full import loop: upload a workbook, watch it process, fix anything that was rejected, and re-import.

Before you start

• You need import permissions on the project.
• Your workbook must be an .xlsx file — not .xls, .xlsm, or a password-protected file — and under 25 MB.
• If you’re starting from scratch, select Download template in the Import workbook drawer for a workbook in the expected shape.

Upload the workbook

1. Open ISOs from the navigation, then select Import workbook… at the top of the list. The workbook loads into the project whose ISOs you’re looking at, so check you’re on the right project first.
2. Drag your workbook onto the upload area, or select browse to pick the file.
3. The upload runs in stages — reserving a slot, then uploading to storage. If it’s taking a while, a note explains the server may be waking up from being idle; that’s normal.
4. If a stage fails, you’ll see what happened (for example, an expired upload link) and a Try again button — nothing is queued until you confirm the mapping in the next step.

Map your columns

Once the upload finishes, a Map your workbook’s columns sheet opens — this is where you tell MaxTrax which of your workbook’s columns are which, before anything is queued for processing.

• Each source column is pre-named with a best guess and a small badge explaining why: Header match (your column heading matched a known field), Value match (the values in the column looked like the right shape — a date, a size, an ISO number), or Remembered (a saved profile for this project used that column before). A column MaxTrax couldn’t guess is marked Needs you, along with a running count like “22 of 25 recognized · 3 need you.”
• Nothing is applied automatically — review each column’s Target field dropdown and correct any that are wrong or unset. A column with no target is left parked (named, not silently dropped) rather than mapped to the wrong field.
• If your project has saved profiles from earlier imports, you can Apply one to fill in the whole mapping at once, or Forget a profile you no longer need. Check Save this mapping as a profile for next time and give it a name to remember your choices for future imports of the same workbook shape.
• Select Confirm and start import when the mapping looks right, or Cancel import to abandon this upload without starting the import.

Watch it process

Once confirmed, the run’s detail page polls automatically and shows:

• Status — Queued, Processing, Completed, Completed with errors, Failed, or Failed — needs attention.
• Rows processed and rows rejected so far.
• Chunks completed, since large workbooks process in pieces.

Fix rejected rows

A validation report appears once the run finishes, listing each rejected or flagged row’s sheet, row number, field, and reason. For rows on the Weld or Inspection sheets, a Fix link jumps straight to that record filtered to the ISO in question. Use the sheet, severity, or search filters to narrow a long report; a Hide button lets you tuck away rows you’ve already dealt with while you work through the rest.

Use Download validation report (.xlsx) to save the report as an Excel workbook — handy for sharing the rejections with a colleague or fixing them in your source spreadsheet. A fresh download link is generated each time you click, so you never land on an expired one. The link itself is short-lived, so download the file rather than saving or forwarding the link.

A rejected row is skipped, not partially applied — the rest of the workbook still imports normally around it.

Flagged rows (imported, but worth a look)

Some rows are flagged rather than rejected — either the row imported and something about it is worth a look, or the row was deliberately ignored in favour of an earlier one. Use the Severity filter to show just these. The kinds that appear:

• Duplicate weld — the row matched an already-existing weld on the ISO; its metadata was re-applied to that weld rather than creating a new one.
• Repair label with no matching parent — a weld labeled like a repair (for example, ending in R1) couldn’t be matched to a predecessor weld on the ISO, so it imported as an ordinary, unlinked weld. Select Link to parent weld… on that row to search for and link the correct parent weld — this resolves it right away, with no re-import needed.
• Weld listed twice in the workbook — the same weld number appears more than once on one ISO. The first row wins; the later row’s values were not imported. If the two rows differ (a different welder, heat or filler, say), decide which is right and re-import.
• ISO listed twice in the workbook — the same drawing number appears more than once on the ISO sheet. Same rule: the first row wins and the later row’s ISO values were not imported.
• Number could not be read — a numeric cell wasn’t a plain number, on a row whose values were being discarded anyway, so the cell was ignored rather than rejecting the row.

Re-import

1. Fix the rejected rows, either directly in MaxTrax (via the Fix links) or back in your source workbook.
2. Under Re-import a corrected workbook, upload the corrected file the same way as before.
3. The new run appears in your import history (Edit in Excel → Runs & history), and MaxTrax can compare it against the previous run — showing which rejections are now resolved, which are still failing, and which are new.

Undo an import

If a workbook went in wrong, you can undo the whole run yourself — no need to raise a support request. You’ll need project administrator access, and the run has to have finished processing.

1. Open the run from your import history — Edit in Excel → Runs & history.
2. Under Undo this import, read the summary of exactly what will be reversed — for example “3 ISOs, 42 welds, 12 inspections”. This is counted from the live data, not from what the run originally reported.
3. Select Undo this import…, then confirm.

What an undo does and doesn’t do:

• It reverses only what that run created and still owns. Rows from any other import, rows that already existed, and rows anyone has edited since the import are never touched — once you correct an imported record by hand, it belongs to you and an undo leaves it alone.
• Nothing is deleted outright. The records are deactivated and drop out of your grids and reports, and the change is recorded against your name in the audit trail.
• If any of the rows sit under a signed ISO or a signed test package, the undo is refused altogether and lists the frozen rows. Signed records are certification evidence, so nothing is quietly removed from underneath one — and the rest of the import isn’t half-reversed either.
• If the import changed between the moment you opened the page and the moment you confirmed, the undo stops and asks you to refresh, rather than acting on a picture you never saw.

Restore an import you undid

For 30 days after an undo, the same panel offers Restore this import, which reactivates exactly the records that undo removed — never anything else. After 30 days the undo is final and the records stay deactivated. A restore is refused if a record was signed while it was deactivated, since putting it back would change what that signature covers.

What happens next

• Rows that import successfully become real ISOs, welds, inspections, and film intervals in your project — the same records you’d create by hand.
• Every run stays in your import history — the Runs & history tab on the Edit in Excel page, which is the single record of every Excel job however it started. It shows who ran it and how many rows processed and rejected, so you can always see what happened and when.

Related

• Troubleshooting: import rejections
• Getting started — ISO, weld, and status vocabulary.