howto
CSV and Excel Format
CSV and Excel headers AutoAssemble reads when assembling models in Creo.
CSV and Excel (.xlsx) share one header-row parser. The first row is headers (case-insensitive). Blank rows and rows with an empty model name are skipped.
The file dialog groups these as Auto Assemble File. Run the command with Assemble from a File. Sibling formats: JSON Format, XML and NWF Format. Worked jobs: AutoAssemble Examples.
Two header modes
Tree builder — requires
MODEL_NAME,LEVEL, andTYPE(orMODEL_TYPE). Builds nested assemblies. First data row must be LEVEL 0 (the top assembly). LEVEL may increase by at most 1 per row. Walkthrough: File-Driven Model Tree.Mate into the current assembly — requires
MODEL_NAME(aliasMODEL_ID). Optional CSYS, interface, designation, and mate-to columns. Every row is assembled into the selected assembly. No LEVEL 0 row. Walkthroughs: Schematic Assembly, Assembling Backshells to Connectors.
Tree builder
csvLEVEL 0 defines the top assembly (not assembled as a child). If Creo already has a current assembly, AutoAssemble still reads that row as the file’s top model name, then uses the selected assembly as the output.
If a named model does not exist and Create Models if Not Found is on, AutoAssemble creates it from the default start part (or empty if that start part cannot be copied).
Mate into the current assembly
csvDefault CSYS names: part PRT_CSYS_DEF; assembly ASM_DEF_CSYS (fallback ASM_CSYS_DEF). MATING_CSYS of <DEFAULT> uses default placement. Empty MODEL_CSYS uses the placing model’s default CSYS.
Identity columns
Header | Aliases | What it does |
|---|---|---|
|
| Creo model name. Required in both modes. Family-table instances need the full name, for example |
|
|
|
| BOM indent. 0 is the top assembly. Required for the tree builder. | |
| Refines type — for example PRT + SKEL is a skeleton part. Skeletons are added as skeletons, not packaged parts. Bulk, skeleton, and harness creation uses | |
| Start-part / template model name when creating a new model. | |
|
| Model common name. |
Designation and grouping
Header | Aliases | What it does |
|---|---|---|
|
| Designation applied to the assembled component. How it is stored is the Designator method — see Designator. |
| Stored label only. Common values: | |
|
| Model-tree group. Nested groups use |
| Named color or RGB string. |
Mating columns
Three roles: CSYS or interface on the component being placed, which existing component receives it, and CSYS or interface on the receiving side.
Role | Preferred header | Aliases |
|---|---|---|
CSYS on placing model |
|
|
CSYS on receiving model |
|
|
Interface on placing model |
|
|
Interface on receiving model |
|
|
Mate-to component (designation) |
|
|
Mate-to port / CSYS on that component |
|
|
CSYS-to-CSYS does not need mate-to component columns. Mating onto a designated component needs MATE_TO + CONNECTED_TO_PORT and either both interface columns or both CSYS columns. Organization default interface names are not applied if those columns are blank.
Anything listed as MATE_TO is assembled before the rows that point at it, so connectors do not have to appear first in the file.
Offsets, drawings, and parameters
Header | What it does |
|---|---|
| Translation applied to the placement. Headers such as |
| Recognized but rotation is not applied. Translation only. |
|
|
| Drawing name. Skip if blank. |
| Optional start drawing. |
| Model parameter |
| Component (feature) parameter |
| Cabling connector parameter |
Any other header | Carried as an extra value (typically a component parameter). Names cannot contain spaces. |
| Ignored. |