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. 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.
  2. 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.
  3. To the Subassembly Only (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.

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 this Subassembly Only” 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

    • Toolbox Release Notes | Build 23.1.0921.641

      The following release notes apply to Toolbox build 23.1.0921.641 Cumulative Library Updates Fix Figure 1: Cumulative Update issue. There was a bug noted by users while attempting to download the Foundation Library’s phase 1 cumulative update and ...

    • Microvellum Foundation Library Release Notes | Build 23.0919

      Additions Added new product Master Double Sided Cabinet. Added “Horizontal Handles Centered” global option to all doors. This is available for all tab pulls, handles, and knobs. Added a new DRAWRECTANGLE 2D plan token to the door subassemblies. This ...

    • My Cases: Case Details

      Once you've logged into the Client Portal and navigated to the My Cases area, simply click on the case title to access the case details page. Here, you can thoroughly review the case description, append additional comments, upload attachments, and ...

    • My Cases: Overview

      Once you've logged into the Client Portal, accessing your support cases is a breeze. You can simply click on the "My Cases" icon in the flyout menu or choose the "View Cases" button conveniently placed on the Welcome page. Inside this section, you'll ...

    • Uploading Attachments to Support Cases

      Support case attachments are files or documents attached to a support case or ticket, serving the purpose of providing additional information, context, or evidence relevant to the reported issue. These attachments can encompass a wide range of file ...