Step by step

1. Open Table and choose the imported, user-defined or snapshot data you intend to work with.
2. Use a stable size key and complete dimension values. Review all columns before changing data.
3. Edit supported cells, choose Save changes, then Use selected row to verify the Designer result.
4. Connect Choose Size outputs to the required object inputs and expose only meaningful public controls.
5. Test the intended sizes and select only valid configurations for export.

Three different roles

A lookup table maps keys to values. A snapshot captures a parameter state. A public/Main Parameter exposes a user decision. One does not automatically replace the others.

Validation and editing

Duplicate or blank keys, invalid numeric values and invalid empty tables should be corrected before saving. Discard draft abandons uncommitted edits. Reset import tables is a deliberate reset, not a routine refresh.

Discovery scope

Source-table discovery supports recognised literal arrays/dictionaries and lookup patterns. Dynamic, encrypted, external-file or arbitrary helper-generated tables are not generally supported. Some structures are protected from resizing or rewriting.

Source changes

If the underlying Python source changed after table edits, a safe reapply/reset may be required. Do not force a saved source patch onto different code.

Nominal selections

A declared option is not proof that all source functions can build that option. Validate each published size. Two variants sharing one nominal diameter may not appear as two distinct nominal entries in Plant.

Keep in mind

• Do not invent missing dimensions or infer that a parameter changes geometry when the source never uses it.

Keep building