Skip to main content

Understanding the Subassembly Save Levels

J
Written by Jordan Munoz

Subassembly Save Levels

When working in the Subassembly Prompts, there are different save options located at the bottom of the interface. Because subassemblies are shared across a project, multiple save levels have been incorporated to allow you to create “unique” subassemblies when changes across the project aren’t desired. Subassemblies can be saved accordingly: 

  1. Save to the Project

    1. Save to Current Row – Saving to the row level means that only that particular subassembly in a product will receive the changes that were made to the subassembly. If there is multiple of the same subassembly in a product, it will only change the one being accessed and saved.

    2. Save to the Product - Saving to the product level means that all subassemblies in a product, with the same subassembly name, will receive any changes that were made to the subassembly. This save will not overwrite any unique subassembly that already exists in the product.

      1. Note: This save will not overwrite any unique subassembly that already exists in the product.

    3. Save to the Project - Saving to the project level means that all subassemblies in the project, with the same subassembly name, will receive any changes that were made to the subassembly.

      1. Note: This save will not overwrite any unique subassembly that already exists in the product or project.

    4. Save to Project as New Subassembly – This option is used to create a new subassembly, at project level, from an existing subassembly. You will need to give it a unique name. The default name will be the one you started with appended with “Copy”.

  2. Save to Library – It is not recommended to do this in a live project that may have project specific settings within a subassembly. This option would typically be used when creating a new or updating an existing subassembly for your library for future use.

    1. Overwrite Existing – This will overwrite the subassembly, with the same name, at the library level making any change a permanent change from that point forward.

    2. Save as New Subassembly – If using the Save to Project as New Subassembly was selected this is typically selected as well. The unique name will automatically populate. If the new subassembly is only for a specific project, you would not select “Save to Library”.

When working with subassemblies, it is important to think about the level at which the subassemblies will be saved. By default, the Subassembly Prompts will have the save option “Save to Current Row” selected. 

Did this answer your question?