Modeling tree nodes [AX 2012]

Updated: March 21, 2011

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The modeling tree is a configuration program and is constructed from various nodes of different types.


This information applies only to Product builder.

The following table contains the principal node types that are available:



Code node

Used to include X++ code in a product model.

IF node

Used to inquire whether a certain condition is met. If it is, the operations described under the subnodes attached to the IF node will be performed.

Switch node

Used to inquire whether the value of a specific variable (the switch value) is equal to one of several possible outcomes.

The outcomes (the case values) tested for are defined as a set of case subnodes.

If the switch value is equal to the case value, the subnodes of the Case node are run.

You can also specify what should occur if no case value is equal to the switch value.

FOR node

Used for repeating the same operation (the functionality defined in its subnodes) many times.

BOM node

Inserts a BOM line into the bill of materials that is being configured by the product model.

Route node

Inserts a route operation into the route that is being configured by the product model.

Insert default route

When a default route has been added to the product model, route nodes for the default route are inserted.

Default node

Can be used to insert either a default route, a bill of materials, or a route.

Table node

Used to obtain values from one or more fields in a table.

Simple node

Used for simple calculations.

Message (Information, Warning, Error)

Inserts an information message, a warning, or an error message.

Several, but not all, of these principal node types can have subnodes attached to them.

  • Under the BOM node and Route node, you can attach a Document handling node that contains a document reference.

  • The Switch node and IF node are used to make decisions in the modeling tree. Both of these node types have special subnodes that can start new branches in the modeling tree. Each branch represents one of the choices that you can program the product model to make, based on values are that are selected for its modeling variables.

  • Under such branch nodes, and also under the Case node, you can attach nodes to each principal type, as listed in the Node types table.

Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions