Overview: Subassembly Save Options

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 it in the project.

We redesigned the subassembly save options screen to make it easier to understand how to save a subassembly back to the various save levels.  In other words, you may save it to the project at various levels, to the library, or both the project and library.

We have also made it easier to save the subassembly back to the library as a new subassembly and to the project as a new subassembly as well. You can save it to the project with one name, and the library with a different name.

The Subassembly Save Options interface will display when you have been working inside the subassembly and click the Save button, or the Close Subassembly button. You will be asked if you want to save the subassembly, and if you click Yes, the Subassembly Save Options screen will display, similar to Figure 01. 


Fig. 01 

Save to Project

We have listed the options below for saving to the project. You may select only one of these options.
  1. Save to Current Row – saves the modified data to only the specific row of the subassembly instance without saving it to the same subassembly on other rows. For example, you may have more than one “Adjustable and Fixed Shelves” subassembly instance in a starter product. You may save your modifications to only one of them using this option. 
  2. After you save a modification at this level, the program assigns the color RED to the subassembly to identify it as having been saved to the row containing the current subassembly.
  3. Save to Product – saves the modified data to only the current product. Other products within the same project will not be affected.
  4. After you save a modification at this level, the program assigns the color YELLOW to the subassembly to identify it as having been saved to the current product containing the subassembly.
  5. Save to Project Overwrite Existing – overwrites the existing data in all products in that project that contain the subassembly.
  6. After you save a modification at this level, the program assigns the color GREEN to the subassembly to identify it as having been saved to the current project.
  7. Save to Project as New Subassembly – creates a new subassembly that is thereafter available for use in other products within the project. Enter the name of your new subassembly in the box provided.
  8. After you save a modification at this level, the program assigns the color GREEN to identify it as a new subassembly in the current project.
    1. You may also use the sub-option “Assign to current row” of his option to further minimize keystrokes. This option saves your modifications to the current subassembly instance AND creates a new subassembly.

Save to Library

We have listed the options below for saving to the library. You may select only one of these options.
  1. Overwrite Existing – overwrites the existing subassembly in the library data. A warning message in red will display when this option is selected.
  2. Save as New Subassembly – creates a new subassembly that is thereafter available for use in other products within the library data. Enter the name of your new subassembly in the box provided.

Colors Assigned to Saved Subassemblies

See Figure 02 for a chart listing the colors the program assigns to saved subassemblies depending on the level at which they were saved. 

Subassembly Save Level
Color
Current Row  (Subassembly) 
Red 
Product 
Yellow 
Project 
Green 
Fig. 02 

Figure 03 shows the colors in the subassembly program interface. 


Fig. 03

Figures 04 - 06 show the colors in the subassembly spreadsheet editing environment.


Fig. 04


Fig. 05


Fig. 06

As you can see from the description above, the new subassembly save options give you much finer control when working with subassemblies in your library data.


    • Related Articles

    • 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 ...
    • 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 ...
    • 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 ...
    • 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 ...
    • Working Within the Subassemblies Tab

      Working Within the Subassemblies Tab The Subassemblies tab is where the subassemblies for the product are located. The majority of library products contain subassemblies. Subassemblies are products within products. Subassemblies can be added manually ...
    • Recent Articles

    • Toolbox Release Notes | Build 24.1.1105.641

      The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...
    • Microvellum Foundation Library Release Notes | Build 24.1025

      The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...
    • Toolbox Release Notes | Build 24.1.1030.641

      The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...
    • Toolbox Release Notes | Build 24.1.1010.641

      The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...
    • Toolbox Release Notes | Build 24.1.1001.641

      The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...