Codaform
EN
Download
The Codaform handbook

The documentation articles are available in English.

Native export

Export a component to Plant 3D™

Publish the current design or selected valid sizes into the connected Plant project, then place a new instance to verify the result.

Where to find it
Export > Export component
When to use it
Delivering reusable catalogue/spec components
On this page

Step by step

  1. Open the intended Plant project drawing and confirm the project connection.
  2. Validate Designer geometry, units, public inputs and all required ports.
  3. Open Export component and review the current design and available table/snapshot sizes. Check only the valid rows to publish.
  4. Use automatic destinations unless a deliberate supported project destination is required under Advanced.
  5. Review family identity, descriptions, part numbers, connection metadata and dimension behaviour.
  6. Choose Export component and wait for the reported outcome. If it is uncertain, use Check export result before retrying.
  7. Place a NEW instance from the target spec and verify shape, colours, physical dimensions and actual pipe connections.

Family identity

Re-exporting the same family updates its recognised entries. Preserve identity deliberately. Existing drawing instances are not automatically replaced or regenerated merely because a family was re-exported.

Checked sizes

Selected rows form the export batch. Unchecked recognised sizes and unrelated families should remain protected; export is not a general published-size deletion tool.

Automatic and fixed dimensions

Automatic uses the native parametric designation for rows with public geometry inputs; rows without public geometry inputs remain fixed. Fixed catalogue sizes is an explicit choice when dimensions should not be edited through that path. Verify ordinary Plant Size and dimension properties on a newly placed fitting.

Connection data

Nominal size, physical outside diameter and port position/direction are separate concepts. Review each connection. No general DN-to-OD or DN-to-NPS standard mapping should be assumed.

Completion and failures

A stage error and an unknown timeout are different outcomes. Read the receipt/status and actual publication state. Do not assume that every failure means no files were written, or that a saved script alone means the spec is ready.

Keep in mind

  • Keep the same running Plant session for normal repeat exports after bridge installation; use a fresh placed instance to inspect a new geometry revision.

Keep building

Documentation