Table extension point

You can also control whether those actions on the table are allowed. For CDFs, you can set defaults, add validations, etc. For standard fields, you can also add validations, etc.

Examples:

• When an Item is added to or updated in the Item table, to update a CDF that holds the last modification date.
• Make a CDF a required field if the Item is of a certain type.
• Block the adding of new Sales Order Lines for a Sales Order when a CDF on Sales Order level has a certain value.
• Do additional validation on a standard field.

A table extension is an extension to the Data Access Layer (DAL) of the table. Although for the table itself the DAL may not be implemented.

For background on hooks, validations, setting error messages, return values, etc. see the DAL chapters and functions in the Infor ES Programmers Guide (Infor Customer Portal KB2924522).

This diagram shows the position of the table extension:

LN sessions manipulate data in the LN tables. The hooks of the table extension are executed both from the data access layer and the runtime layer. The latter happens in the case the data access layer has not been implemented or is bypassed (for performance reasons) for certain LN tables. The table extension is applied regardless of the techniques used in the standard application.

The Create/Convert to runtime process also invokes the table extension to determine whether custom indexes must be created, changed or deleted.

The table extension point, has these extension types:

• Table
• Customer defined field logic
• Standard field logic
• Custom index
• Calculated field