Business Objects - Configuring in a Report Dataset
This tutorial is the first in a series of three that demonstrates how to configure Microvellum Business Objects in a sample report dataset. Click here for an overview of how they are intended to be used.
We will set up the dataset to contain the following global variables from the default Microvellum library:
Cabinet Back Construction / Back Construction Selections
Base Back Construction (Captured Sides and Bottom)
Tall Back Construction (Full Captured)
Upper Back Construction (Full Captured)
Sink Back Construction (Captured Sides and Bottom)
- Open Toolbox and click: “Toolbox Setup > Design Reports > Design Manufacturing Report > New Report From Existing > Product Detail – Static JPG.”
- Report Setup box: name the new report “Business Objects - Product Detail.”
- Report Setup box: check only the checkbox for “Projects” in the Microvellum Factory database type.
- Report Setup box: leave the default tables checked.
- Report Setup box: click the options button for “Business Objects.” In the section containing the checkboxes for the Database Tables, click all four options - even if you don't need access to all of them. This will give you the greatest number of related data points possible and will prevent any confusion about what data is available. It does not discernibly increase the overhead of the report.
Fig. 1
- When the Business Objects option button is selected, there are two additional buttons activated: Add Global Variables and Add Product Prompts. To use the Business Objects for data of either type, you must click the corresponding button and add the specific names to the list. The names must be the exact format of the defined name. For example, if the defined name for a prompt is "Right_Fin_End," you must not enter "Right Finished End." You must enter it exactly, "Right_Fin_End." The same is true for global values. For example, if the name of the variable is “Base Back Construction,” you must enter “Base_Back_Construction.” Do not try to click Add Global Variables or Add Product Prompts button a second time to view the data you have added until after clicking the OK button for the Report Setup box, as described below.
- Once you have configured the Business Objects in the Report Setup box, click the OK button. Re-open that report and click the button Edit Data Source again if you want to verify the data just entered. Again click Business Objects > Add Global Variables and Business Objects > Add Product Prompts to view the data that will be included in the report dataset. If it’s wrong, add or revise the data and click OK. Otherwise, click Cancel.
Fig. 2
Fig. 3
- Click the Designer button and then the Dictionary tab to view the available data. Expand the Data Source named "EstimateProject" and view the 'tables' below that parent entry.
Fig. 4
- Right-click the table named “EstimateProject_GlobalVariables” and click "View Data" to preview the results of your Business Object global variable configuration.
Fig. 5
- Right-click the table named “EstimateProject_Products” and click "View Data" to preview the products included in the results of your Business Object product configuration.
Fig. 6a
- Right-click the table named “EstimateProject_Products_Prompts” and click "View Data" to preview the individual prompt values included in the results of your Business Object product prompt configuration. You will notice that the field _ID in the Products table corresponds to the field _parentID in the Prompts table. Thus, in our sample, the two rows in the Prompts table with a _parentID of zero (0) belong to the row in the Products table with an _ID of zero (0).
Fig. 6b
Below is a summary of the EstimateProject data source schema.
-
EstimateProject = project name and ID.
-
EstimateProject_GlobalVariables = global variable name of each global specified in the configuration of the object, global value, ID, and parent ID.
-
EstimateProject_GlobalVariables_Value = ID, parent ID, global values split into one digit per record (row) for multiple digit global values.
-
EstimateProject_Rooms = room name and ID.
-
EstimateProject_Rooms_Products = product name, product item number, ID, and parent ID.
-
EstimateProject_Rooms_Products_Prompts = prompt name of each prompt specified in the configuration of the object, prompt value, ID, and parent ID.
-
EstimateProject_Rooms_Products_Prompts.Value = ID, parent ID, prompt values split into one digit per record (row) for multiple digit prompt values.
- There are limitations in the data available if you don't select all tables when setting them up in the "Business Objects" option button (Global Variables, Product Prompts, Products, Project).
- To preview that data as described above, you must first select a project before working in the report designer.
- When configuring the Global Variables, you must add the specifically defined name values for each global.
- When configuring the Prompts, you must add the specifically defined name values for each prompt.
- The Business Objects do not support relationships between the Business Object and the factory or work order dataset objects.
Tutorials for setting up your report to display the Business Object data are found elsewhere in the Help Center.
Related Articles
Business Objects - Configuring a Report to Display Globals (with Subreports)
This is the second in a series of three tutorials that demonstrate how to configure Microvellum Business Objects in a sample report. This tutorial assumes that you have a basic understanding of Business Objects in Microvellum reports. Click here to ...
Business Objects - Configuring a Report to Display Globals (with Databands)
This is the third in a series of three tutorials that demonstrate how to configure Microvellum Business Objects in a sample report. This tutorial assumes that you have a basic understanding of Business Objects in Microvellum reports. Click here to ...
Using Business Objects in Reports (Overview)
The term "Business Object" is used in Microvellum to describe an object or entity that encapsulates or contains data. The Microvellum Business Objects are used in reports. They are set up when configuring the report dataset and contain either the ...
Report Training Tutorial 1: Report Designer Basics
This is the first of a series of five Reports Training Tutorial videos. This video presents some basic concepts that will be useful for first-time users of Report Designer. By the end of this video, you will have some familiarity with the user ...
Report Training Tutorial 5: Configuring a Master-Detail Report
This is the last in a series of five Report Training Tutorial videos. In this video, we'll develop a new Master-Detail report and introduce new concepts, including using Sub-Reports to better organize your report and make report development a little ...
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 ...