Adding the Product Description Prompt Data for Reporting
Adding the Product Description Prompt Data for Reporting
As a result of the report structure and report
specification requirements, sometimes it is not possible to accurately
reference the prompt "ProductDescription" in a report. An example of
this would be when trying to group on that prompt value. Another example would
be when the report databand structure does not support a relationship between
two dataset tables - such as OptimizationResults or PlacedSheets (part or
material based) and Prompts (product-based).
The procedure in the
attached video allows you to define the ProductDescription prompt value as a
ProductComments1 field, and thus accurately exposes it to reports with complex
data requirements.
The video assumes
that you do not have ProductComments1 already in use for some other purpose. If
it is in use, you may have to reconfigure the existing comments to be located
elsewhere.
Lastly, the video
demonstrates the procedure with a single product. If you need to modify your
entire library and are proficient using the Library Designer, we recommend that
you first back up a copy of your library and proceed to make the modifications
contained in this video using the Library Designer.
Product List The Product List is a module that allows users to make modifications to their products without working directly in the drawing. The following article, detailing the different aspects of the Product List, applies to build 20.1.0826.641 ...
The articles in this section of the Knowledge Base involve working with Lists for display in your reports. To learn more about Lists and how to access the Report Designer, see Creating Lists in Report Designer. This article provides an overview of ...
Some Users tell us that infrequently a report may be displayed that is missing data when previewed. There are various possible reasons for this issue, but one cause may be a defective report dataset definition. This article explains a pre-test to ...
As of build 15.6.221, you now may use the simplified procedure found in the Microvellum Help Center article Processing Station Associates for Reports (Overview) to resolve this issue in addition to the procedure found in this article. Issue : Part ...
Expressions can contain values from data sources. A string representation of the field is used to reference that field from the data source. The proper syntax for the reference is the name of the data source and the field name with a full-stop ...
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 ...
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 ...
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 ...
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 ...
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 ...