Customer Defined Fields

Tailoring is adding functionality to existing components. Tailoring includes the concept of Customer Defined Fields (CDFs).

Those fields can be added to tables, screens, reports, BODs, and BDEs and validation and calculation logic can be defined around those fields.

Use the Customer Defined Fields (CDF) concept to store additional data in the standard Infor LN tables. The CDF definitions are stored separately from the table definitions in the Data Dictionary. For the end user, the CDFs behave in the same way as the standard fields, if defaulting, validations, etc. are built using the CDF logic of the table extension point. The session extension point also has features for the CDFs.

See Customer defined field logic and Customer Defined Field.

CDFs are configured per package combination. This implies that when moving your companies from one package combination to another, the CDF definitions must be present in the target package combination. Otherwise you lose the data in the CDFs.

New export and import procedure

From Enterprise Server 10.6.0.1, PMC is used to export and import CDFs through extensions.

See Exporting and importing CDFs through PMC.

Old export and import procedure

The old procedure to export and import CDFs should only be used to copy CDF definitions from or to LN 10.5 and older LN versions. In the old procedure, these sessions are used:

  • Export Customer Defined Fields (ttadv4291m000)
  • Import Customer Defined Fields (ttadv4292m000)

See Exporting and importing CDFs through ttadv4291m000 and ttadv4292m000.