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

For the people who asked

Each has a working default today. Each answer is a small change once it is known.

Where should a point set live?

Each set is a named Design Group (NX 2606’s successor to the feature group) holding Point features. Export also lists named legacy feature groups. Is a Design Group the right home, or should sets be a single Point Set feature, a body, or something read from Teamcenter?

Which worksheet?

Import reads the first worksheet of the workbook. If your files keep several tables, a sheet picker is a small addition.

Units

Coordinates are read and written in the work part’s units, and the dialog says which. Should a file be allowed to declare mm in an inch part, and be converted?

Point count

Here 0 means every row until the first empty one, and asking for more points than the file holds is refused rather than shortened. Does that match how the original tool treats the count?

Replace semantics

Replace deletes the set’s points and creates the file’s, keeping the set’s name and place in the model history. Features that referenced the old points would need re-pointing. Should Replace move the existing points in place when the counts match?

Where the commands sit

A Points@ ribbon tab and Menu › Points@, loaded from the folder through custom_dirs.dat. Your site may prefer them in an existing tab or group.

Not yet covered

Verified in native NX on this project’s sample part and files. Not yet run on a production model, a Teamcenter-managed part, or the original tool’s own files side by side.