ICD save modes: Create/Update vs. Overwrite vs. Revise

Connectivity Hub has three distinct ways to save an ICD, and picking the wrong one either silently drops prior connectivity data or fails to remap something you intended to change. Know the difference before saving.

Create/Update ICD

Creates a new ICD, or adds to an existing one.

• Preexisting connectivity is retained.
• Supports iterative ICD publish — i.e. you can save partial connectivity now and add more later without losing what's already there.

Use this when you're incrementally building up an ICD's connectivity over multiple sessions, or when several components/schematics contribute pieces of the same ICD over time.

Overwrite ICD

Creates a new ICD, or completely overwrites an existing one.

• Preexisting connectivity is removed.
• Supports remapping connectivity to pins — because the slate is wiped clean, this is the right choice when you need to re-derive an ICD's connectivity from scratch (e.g. after a significant design change) rather than accumulate on top of stale data.

Revise ICD

Creates a new ICD with the next alpha-numerical revision.

Use Revise when you want to preserve the prior revision as a historical record (standard revision-control behavior) rather than mutate the current one in place — this is the only one of the three modes that produces a new, separate revision instead of modifying the ICD you started from.

Quick decision guide

You want to...	Use
Add more connectivity without losing what's already saved	Create/Update ICD
Start the ICD's connectivity over from a clean slate	Overwrite ICD
Keep a permanent, separate record of this version before changing it further	Revise ICD

See also: Saving ICDs from schematics, which uses this same New/Merge vs. Overwrite distinction when saving directly from a schematic device.