Infor LN DAL Hook Checklist (Free, Exportable)

0%

0 of 28 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

Design and hook choice

The rule truly belongs in the DAL (must hold for every entry path), not only in one session scriptCRITICALObject-level hooks (new, save, destroy) are used for whole-record rulesField-level hooks are used for single-field validation and defaultsBefore hooks validate and reject, after hooks only follow upCRITICALThe change is in the customer VRC, not in the standard componentCRITICALPurpose, author and date are documented in the script header

Validation and error handling

Every rejection returns a clear message from a message code, not hard-coded textCRITICALReturn values are checked after every DAL or database callRules work for create, update and delete paths separatelyBlank, zero and unusual enum values are handledNo silent failure: errors are surfaced to the callerCRITICALBehavior is defined when called from import, BDE or integration, not only the UI

Data integrity and transactions

The hook does not commit or abort transactions on its own unless designed toCRITICALRelated tables are updated in the same logical transactionCross-company access is deliberate and uses the right company numberLocking behavior is understood and rows are not held longer than neededDerived values are recalculated when their inputs change

Performance

No SQL select inside a loop that could be a single set-based queryCRITICALQueries use indexed fields in the where clauseHeavy logic is not placed in a hook fired for every line of a mass updateRepeated lookups are cached in a variable for the callTiming was measured with realistic volumes, not one record

Testing and upgrade safety

Tested through the session, an import and an integration pathCRITICALRegression test covers the standard behavior near the hookA rollback plan exists for the transport or VRC changeThe customization is listed in the upgrade inventoryStandard functionality was checked to see if it now covers the needA reviewer other than the author signed off

Count the items you can tick. Treat unticked critical items as blockers before promoting a DAL change to production.

Customization inventory help

Optional: discuss how to document DAL and 4GL customizations before an upgrade.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Run it as a peer review before a DAL change goes to test and again before production. Tick each item you can confirm from the code or from a test, and treat unticked critical items as blockers. Attach the exported list to the change ticket so the reasons for each decision are traceable. It works equally well for a new hook and for reviewing an old customization you inherited.

Why the DAL, and what hooks are for

A DAL script sits on the table, so a rule there applies when a user saves in a session, when an import writes a record and when an integration calls the object. Hooks are the points where your code runs: object-level hooks around new, save and destroy, and field-level hooks for validation and defaults. Validation belongs before the change is stored, follow-up work after it. Exact hook names and parameters vary by version, so match them to your environment.

Whole-record rules go on object hooks
Single-field rules and defaults go on field hooks
Keep each hook short and call functions for reusable logic

Common mistakes

The usual defects are rules written only in a session script, hard-coded error text, queries inside loops that make mass updates slow, and hooks that quietly swallow an error. Developers also forget non-UI paths: an import or a BDE that bypasses the screen but not the DAL can fail in unexpected ways when a hook assumes screen state. Test the hook through every path, measure with realistic volumes and keep an upgrade inventory so nothing is lost at the next release.

Frequently Asked Questions

What is a DAL in Infor LN?

The data access layer is a script attached to a table that enforces rules and defaults whenever data is created, changed or deleted, whether through a session, an import or an integration. It centralizes business rules instead of repeating them in each screen.

When should I use a DAL hook instead of a session script?

Use a DAL hook when the rule must apply on every path to the table. Use a session script for presentation and behavior specific to one screen. Many solutions combine them, with data rules in the DAL and user interface logic in the session.

Why is my DAL change slow on mass updates?

A hook runs for each record, so a query or heavy calculation inside it multiplies. Look for selects inside loops, missing index use and repeated lookups, and measure with realistic volumes before promoting the change.

Is this checklist valid for every LN version?

The review principles hold across versions, but hook names, parameters and tools differ. Check specifics against the documentation for your version and a known working script in your environment.

If you want a faster inventory and review of DAL and 4GL customizations across your LN estate, we can discuss an on-prem assistant that reads and summarizes them.

Talk to an Expert Explore More Free Tools

Related Tools

Infor LN & Baan

More Infor LN & Baan tools

See all

Infor LN DAL Hook Checklist for Developers