NX Automations · NX dialogs on a ribbon tab

Imports, exports and replaces sets of points with Excel: three dialogs on a Points@ ribbon tab, each point set a named group in the model.

Verification passing on NX 2606.5001 · 2026-10-03 · repo b9f63ea

Excel in, point sets in NX, Excel out: the file contract, the checks before anything lands, where the points live, and the export. Click to zoom.

The file, both ways

LayoutOne point per row, one coordinate per column, starting at the cell you give (A2 when row 1 is a header).
Coordinate systemXYZ reads three columns. XY, YZ and XZ read two, and the missing axis is 0. Export writes the same columns.
Point countHow many rows to read. 0 means every row until the first empty one.
Formats.xlsx (the first worksheet on import; one worksheet per set on export) and .csv (one set).
UnitsThe work part’s units, shown in the dialog (“20 points found from A2 (in)”).

Where the points live

Each set is a named Design Group, NX 2606’s successor to the feature group, holding one Point feature per row. It shows in the Part Navigator under its name, survives save and reopen, and Export lists named legacy feature groups too. Every Import, Replace and Export is a single Undo mark.

Refused, never half-done

A cell that is not a numberRefused, naming the cell: “cell B2 holds ‘five’, which is not a number”.
A row with a missing coordinateRefused, naming the empty cell. Never read as 0.
More points than the file holdsRefused: “asked for 25 points from A2, but the file has only 20 there before an empty row”. Never a shorter import that looks complete.
A set name that already existsRefused on Import, pointing to Replace.
A header row with the start cell in row 1Refused on Export: the header needs a row above the first point.
Several sets to one .csvRefused: a .csv holds one set; save as .xlsx for several.