Save Subassembly to Template Check Prompts (Reference)

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 Center for an overview of this new interface.

Getting There

To begin, use the command Edit Design Data on a product to edit a prompt value of a subassembly.

Right-click on a subassembly row and select Show Subassembly File. Select the prompt tab at the bottom of the subassembly spreadsheet. Choose the desired formula-driven value and hard-lock it with a new value (see example below).


Fig. 1 – Example of Replacing a Formula with a Value


The “Subassembly Save Options” interface displays after saving the hard-locked values.


Fig. 2 – Subassembly Save Options


This interface offers two ways to save a subassembly – Save to Project, or Save to Library.


Fig. 3 – Save to Project Options

Fig. 4 – Save to Library Options

Saving Changes to the Project

Here is a list of the commands available when saving changes.

Save to Current Row  – Saves changes only to the current row.

Save to Product  – Saves changes only to the product.

Save to Project Overwrite Existing  – Saves changes at the project level and overwrites any existing data in the project.

Save to Project as New Subassembly  – Saves the subassembly to the project as a new subassembly. The user assigns a name to the new subassembly in the box and allows assigning it to the current row.


Fig. 5 – Save New Subassembly to Project Options

Saving Changes to the Library

If changes are made to subassembly prompts, selecting the radio button Overwrite Existing will activate the button Resolve Prompt Conflicts.


Fig. 6 – Overwrite Existing Activates Button


Clicking on this button will display the Resolve Subassembly Prompts interface.


Fig. 7 – Resolve Subassembly Prompt Interface

This interface provides a clear visual representation of the subassembly prompts changed by hard-locked values in the spreadsheet. It ensures library level subassembly prompt changes reflect the value(s) desired by the user. It enables users to select the checkbox Overwrite With Template. This causes the selected values to be overwritten with the “Template Value.”

Selecting the “Save as New Subassembly” radio button will allow the user to save and name a new subassembly to the library.


Fig. 8 – Save As New Subassembly

    • Related Articles

    • 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 ...

    • Microvellum Data Dictionary

      Microvellum Data Dictionary Introduction This manual is a guide to the Microvellum Factory and Work Order Databases. This manual has four sections. The first section includes this introduction, and the remainder is General Information about this ...

    • 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 ...

    • 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 ...

    • Overview: Passing Prompt Information Between Workbooks (Subassembly)

      We have added the ability to pass custom information from the L! workbook (local prompts) to the S! workbook (subassemblies). Without that ability, the number of prompts is greater, and the complexity of formulas increases. When the formula ...

    • 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 ...