Understanding the Subassembly Save Levels

Understanding the Subassembly Save Levels

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.  

    • Related Articles

    • Overview: Subassembly Save Options

      Microvellum builds 15.5.1405 or higher required. The program has been modified to improve the flexibility of saving subassemblies.  Previously, when creating a new subassembly, the program created the new subassembly in the library but did not create ...

    • Save Subassembly to Template Check Prompts (Overview)

      The purpose of this article is to highlight the new interface and functionality when saving subassembly prompt(s) to the library level. When saving a subassembly back to the template and overwriting it, you can now check the modified subassembly ...

    • Understanding What a Subassembly Is

      Understanding What a Subassembly Is Subassemblies are smaller products inside of another product. Subassemblies are also shared within a project. For example, the subassembly, Carcass Base, is shared across all the base cabinets in a project.  The ...

    • Understanding the Subassemblies Tab

      The subassemblies tab will display the subassemblies that the product is currently referencing. A subassembly works the same way a product does. It contains its own set of parts, hardware, and prompts. A subassembly can also contain more ...

    • Save Subassembly to Template Check Prompts (Reference)

      The purpose of this article is to provide a reference for the new Subassembly Save Options interface. This reference applies to Toolbox builds 15.6.2201 and greater. See  Save Subassembly to Template Check Prompts (Overview)  in the Microvellum Help ...

    • Recent Articles

    • Microvellum Release Notes | Build 26.1.0422.641

      The following release notes apply to Microvellum build 26.1.0422.641. BSB 2026 Microvellum BSB 2026 is now available for download and installation by users with an existing Microvellum BSB subscription. This new version of Microvellum is based on ...

    • Microvellum BSB 2026

      Microvellum BSB 2026 is now available for purchase and download. BSB 2026 introduces the Microvellum software bundled together with the BricsCAD Pro 2026 platform, with all of the accompanying changes and enhancements made after BricsCAD 2025. With ...

    • Microvellum Release Notes | Build 25.2.0406.641

      The following release notes apply to Microvellum build 25.2.0406.641. Label Image Fix Fig. 1: An error noting an incorrect number of Label Images. An issue was reported wherein creating new G-code from an existing work order that was edited using ...

    • Microvellum Foundation Library Release Notes | Build 26.0327

      The following release notes apply to Microvellum Foundation Library build 26.0327. Additions Added new Formula Driven Materials (FDM) and accompanying special FDM project wizard. * New Specification Group “Wizard Formula Driven Materials [FDM]”. New ...

    • Formula Driven Materials (FDM) User Guide

      The formula driven material (FDM) system in Microvellum automates the creation and management of materials within a project. By using predefined lookup tables and intelligent formulas, FDM dynamically generates each material’s name, thickness, and ...