AutoNexit Training 3 min readAT-05

Import an Excel list without guessing the columns

Share

You already have an equipment or I/O list in Excel. You do not need to type it again, but AutoNexit needs to know what each column means. A preview lets you catch the wrong mapping before records are created.

Start with a few rows

Use a copy of the workbook and keep a handful of representative rows for your first attempt. For example, a column called Signal name may need to map to Tag. Seeing similar words is not enough: check the actual values in the preview.

Prepare a straightforward file

  • Put one clear header row above the data. Remove decorative headings and merged cells from the import area.
  • Keep identifiers such as addresses as text when leading zeros matter. Formulas are not accepted as import data; use checked values.
  • Open the correct engineering register, such as Equipment or I/O. The selected register determines the available target fields.
Compare the preview values with the fields you selected.
Spreadsheet import preview

Compare the preview values with the fields you selected.

Preview, validate, then import

  1. 01

    Open the register’s CSV/XLSX import and select the file. Follow the file-size and row limits shown in the dialog.

  2. 02

    Preview the file. For each source column, choose the correct target field and inspect the sample values.

  3. 03

    Choose the duplicate-handling option deliberately. If an existing tag is involved, establish which record should remain authoritative.

  4. 04

    Run validation and read the row errors. Correct the source or mapping, then validate again until the intended rows are acceptable.

  5. 05

    Import the validated rows. Open several resulting records and compare their identifiers and values with the source.

Read the row errors before committing the import.
Import validation results

Read the row errors before committing the import.

A successful upload is only the first check

Confirm that the expected records were added or updated in the intended register. Compare a normal row, a row with an optional field and one that previously failed. Keep the original workbook until you are satisfied with the result.

Find the cause instead of repeating the upload

  • Values appear under the wrong field? Review the column mapping before another import.
  • One row still fails? Read its specific error; changing the heading cannot repair an invalid address or missing required value.
  • A duplicate is reported? Inspect the existing record first. Do not select an overwrite-like policy merely to make the warning disappear.

Frequently asked questions

Will importing edit the workbook on my computer?

No. The selected file is a source for the import, not a workbook that AutoNexit edits in place.

Can I upload a file with only the rows I need?

Yes. Prepare a separate source containing those rows and its header. Check that the preview count matches your intention.

Is an engineering-register import the same as uploading a project document?

No. Import creates structured records. Uploading an Excel file in Project documents stores a downloadable file.

Does the import verify the plant’s actual wiring?

No. It checks supplied data. Comparing it with field equipment remains an engineering task.

Related articles