Engineering

Import, map, validate and export registers

Preview source data, map columns, choose duplicate policy and resolve findings before import.

Use this guide when Import, map, validate and export registers must describe the engineered system with identifiers and relationships that remain useful downstream.

A localized AutoNexit Sample view for this workflow. Sample data is shared and read-only.

Before you begin

  • Import, map, validate and export registers — Confirm the Zone, Equipment and source register, then normalize tags, addresses, versions and network values before entry or import.

If the result is not what you expect

  • Import, map, validate and export registers — If validation fails, resolve duplicate identifiers, incompatible addresses, missing relationships or column mapping errors before accepting the record.

Frequently asked questions

What should I verify before I work with Import, map, validate and export registers?

Preview source data, map columns, choose duplicate policy and resolve findings before import. Confirm the Zone, Equipment and source register, then normalize tags, addresses, versions and network values before entry or import.

How do I know Import, map, validate and export registers is complete and trustworthy?

The expected result is a validated engineering record that can be traced to its equipment and reused by execution without retyping. If validation fails, resolve duplicate identifiers, incompatible addresses, missing relationships or column mapping errors before accepting the record.

Was this guide helpful?

Need help with your own project?

Sign in to send a private support request. Do not include passwords, tokens or private files in the first message.

Open support

Help topics

On this page