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.
- 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.
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.
- Save to Product – saves the modified data to only the current product. Other products within the same project will not be affected.
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.
- Save to Project Overwrite Existing – overwrites the existing data in all products in that project that contain the subassembly.
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.
- 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.
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.
- 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.
- Overwrite Existing – overwrites the existing subassembly in the library data. A warning message in red will display when this option is selected.
- 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.