DAL 1

DAL 1 scripts were introduced in Infor Baan 5.0. A DAL 1 script contains database logic such as logical integrity rules, but it usually does not contain all business logic for the table it belongs to. Very often, business logic is spread across the DAL 1 script and the UI scripts.

Most UI scripts still contain business logic to do the following:

• Make fields read-only.
• Determine which enum constants can be selected in an enumerated field.
• Update a field after a change to a related field.

Therefore, it is difficult to use the DAL 1 scripts for integrations via the LN Business Adapter software: the business logic in the UI scripts is skipped if another application connects to an LN table. Therefore, this logic must be rebuilt in the Business Object Interfaces (BOIs) that provide the connection. If you change the business logic in the UI scripts, you must also adapt the corresponding BOIs.

A DAL 1 script can contain the following types of hooks:

Object hooks.

These hooks operate on the row or record as a whole unit. Object hooks determine if operations on a row are allowed, and specify additional operations that should be performed based on an operation of the row. Examples of object hooks are as follows: Delete the additional employee data in the People package when an employee is deleted. When a sales order line is saved, create a history record of the sales order line. Update the item inventory when a planned stock transaction is created.

Property hooks.

These hooks operate at a field level, and are used to verify valid values and calculate default values for table fields. Examples of property hooks are as follows: Validity check that the Quotation expiration date should be after the Quotation entry date. When adding an employee, the language of the company is the default for the employee’s language.

For details on DAL 1 scripts, see "Data Access Layer" in the Infor ES Programmers Guide (Infor Customer Portal KB2924522).