Input arguments as data objects

Input arguments of a functional map can evaluate to Item or Group type data objects.

Item types

When an input argument of a functional map evaluates to an item type, the type of the corresponding input card must be an item type with the same Item Subclass (Number, Text, Date & Time, or Syntax).

An input argument might evaluate to a number. If the following input argument evaluates to a number, the corresponding input card type must be an item with an Item Subclass of Number:

INDEX (Record:File)

If the input argument is a text literal (for example, "payroll"), the input card type that corresponds to this argument must be an item with an Item Subclass of Text.

Group types

When an input argument of a functional map evaluates to a group type, the type of the corresponding input card must be the exact same group. For example, if the second input argument evaluates to InvoiceSet, the TypeName of input card #2 must be InvoiceSet.

If there is one argument of the functional map, there will be one input card. The TypeName on the input card must correspond to the data object specified in the argument for the functional map.

Functional maps do not require InputData and OutputData settings.

When InputData and OutputData settings exist in input and output cards in a functional map, they are ignored when the executable map is compiled.