Please consult the Online Help File for the most up to date information and functionality.
The BOM to Database plugin runs on a SOLIDWORKS Assembly and exports its BOM directly from the assembly to a database.
This plugin is machine specific and should be installed on each machine where specifications can be created. (DriveWorks Administrator, DriveWorks User, DriveWorks Autopilot, DriveWorks Live.)
This plugin will only run when using Queued Model Generation (Manual or Automatic).
Please see Model Generation Behaviour for information on Queued Model Generation.
The installation file is available from the DriveWorks User Community website at https://hub.driveworks.co.uk/ (login required).
Once downloaded double click the DriveWorksLabsBillOfMaterialsToDatabase.msi file to begin the installation process. DriveWorks and SOLIDWORKS should be closed while installing the plugin.
Once installed the plugin is automatically loaded in DriveWorks.
The plugin is uninstalled from Windows Programs and Features, and will be listed as DriveWorks Bill of Materials Export (Database).
Once installed the plugin can be configured by:
A settings file must be loaded to use the plugin.
Click this button to either browse to an existing settings file or create a new one in the desired location by just typing a filename in to the browse window.
Once the plugin has been configured, this settings file can then be transferred to any other machine that wishes to use the plugin.
The plugin needs to know the name of each assembly it is to run on.
To Add a model to the list
This is the Master Model Name of any captured DriveWorks model minus the extension, and is case sensitive.
To remove a model that has been added to the list
Writing to a database field where the Data Type is set to BIGINT will cause the export to fail.
This allows the connection parameters to be configured
The plugin allows for different options and BOM Templates to be configured for each master model that can be generated from the DriveWorks group.
Once a Model has been selected in the Project List drop down, the rest of the settings can be configured.
Check the box next to each option required for the selected model.
Include Sub Assemblies
When checked will include Sub Assembly information in the Bill of Materials.
Traverse Sub Assemblies
When checked will drill down into sub assemblies to include their parts on the Bill of Materials.
Use SOLIDWORKS Exclude From BOM
When checked will adhere to the SOLIDWORKS setting "Exclude from BOM".
Different Configurations in Different Rows
When checked will create new rows in the BOM for different configurations of the same parts.
Cut List Items on Different Rows
Parts must have a custom property called "DWExportCutList" set to a specific value. This value must then appear as the name of a cut list item specific property.
When checked will add logging information onto the Logging Section in the Settings Dialog.
Ignore Control fields for cut lists
When checked will force non-unique inserts into new rows. Checking this option means that non-unique items will be added to new rows regardless of the control fields set. (Not recommended).
Quantity Custom Property
If entered the quantity value will be summed from this custom property if found in any model, rather than the item count.
The fields selected when configuring the database are populated in the list view as shown.
To map database fields to values to be written into the database:
These fields can be mapped to properties and values in the SOLIDWORKS assembly. Select a field and hit edit to map the fields to a SOLIDWORKS Value. This could be any of the following:
Check the box next to any field that will be a control field.
A control field dictates whether the entry will be written or not.
For each unique component in the assembly the plugin is running on, the plugin will create a record and insert it into the database. When the BOM plugin is running, a progress dialog will pop up allowing the user to see its current task.
Once the plugin has completed compiling all the data for the clone, it will send it to the destination database.