Unlike the modeling variables, calculation variables are invisible in the user dialog box. They can be used for various types of intermediate calculations in the product model, or to fetch data from other parts of the system. For example, if a calculation must be performed by the product model (perhaps to determine material consumption for a bill of materials (BOM) line) or if a value must be fetched from one of tables in Microsoft Dynamics AX, you can define calculation variables to handle these tasks. Calculation variables are created in the form on the tabs listed below. These tabs are located in the upper pane of the form.

Tab page

Description

You can create system variables of the following variable types:

of the , , , and types are useful for transferring information from the order line or the quotation line to the current item configuration.

All system variables can be used to transfer values between parent and child product models.

Note Note

Create only one of each type, but for .


On this tab, you can define calculation variables of the following types: , , , and . Simple variables have no special functionality attached to them. They are just used to hold calculation data.

Here, you can define variables using any Microsoft Dynamics AX extended data type, such as AccountNum, a data type intended to hold account numbers.

Here, you can define variables using any Microsoft Dynamics AX extended data type, such as AccountNum, a data type intended to hold account numbers.

This tab can be used to define table variables. For example, this type of calculation variable can be used within X++ code to handle any table defined in Microsoft Dynamics AX.

This tab page can be used to define class variables. For example, these variables can be used within X++ code to handle any class defined in Microsoft Dynamics AX.

Apart from modeling variables, and variables are the most common variable types used in intermediate calculations and for building the product model's logical conditions.

and variables are intended for users who have some programming experience. Their purpose is to allow the product model's nodes, in the modeling tree, to handle Microsoft Dynamics AX tables and classes.