Limitations and restrictions

All updates that are done in the table extension are part of the transaction that is started in the standard LN application. You cannot call commit.transaction(), abort.transaction() or db.retry.point() from within one of the extension hooks. Doing this can lead to fatal applications errors, or data corruption in the database.

A table extension has no access to the UI. You cannot start sessions or reports.

You can use queries within the hooks of the table extension to read data from the database. Note that the standard LN application and the extension share the same record buffers. This implies that when the extension reads data from the database into those record buffers, the functionality of the standard LN application can be disturbed. To prevent this, explicit binding of variables must be applied, or the record buffer must be saved before your query is executed and restored afterwards.