** NAV Terminology

The following shows descriptions of several terms in the third column:

Properties:

Properties control the appearance and behavior of application objects and all sub-objects. Properties are used to control the appearance of data, specify

default values, specify colors, and define relationships.

C/AL:

C/AL is the language used for writing functions in C/SIDE. In the

previous table, C/AL refers to functions written in this language.

Triggers:

When specific things happen to the application objects, the system

automatically activates a trigger. Inside a trigger, developers can add C/AL code

if they want to modify the default behavior of the application object or extend its

functionality.

Fields:

A field is the smallest unit of information in the database. A field

typically stores information such as a name or a number.

Keys:

A key defines the order in which data is stored in the tables. Speed up

searches in tables by defining several keys to sort information in different ways.

Controls:

Controls are objects on a form or report that display data, perform

actions or decorate the form. Typical examples are command buttons and text labels.

Request Form:

A request form is a form used in a report or a dataport. Before a

report or a dataport is run, a request form appears to let the user specify filters and options for the report or the dataport.

Request Page

: A request page is the request form equivalent in the RoleTailored client.

Data Items:

A data item is a building block used for defining a model of data

when creating a report or a dataport. By using a hierarchy of data items,

developers define which data to include in the report. A data item represents a table and when a report is run, the system cycles through the records in the associated table. In a report, a data item can have one or more sections.

Sections:

A section is a substructure of a data item. A section is where controls are placed to display information. Generally, sections are used to define the body, header, and footer in the report.

NodeName:

NodeNames are used to specify the name of a node in an XML

document. The name specified is inserted in theNodeName field of the

XMLport Designer of the element or attribute in question.

NodeTypes:

This property is used to specify whether an XML object is an

element or an attribute.

Menu Node:

A Menu Node can be either a Menu Group or a Menu Item.

Menu Group:

A Menu Group is a collection of Menu Nodes.

Menu Item:

A Menu Item is the lowest level of the menu tree. It is associated

with a specific application object.