Optional$overrideSet properties not directly supported by this API.
OptionalactiveWhen false, disables this definition and all its associated rules.
Defaults to true.
The matcher table that drives the lookup — must be a table that extends dl_matcher
in sys_db_object. Each row in this table defines a set of field values; when all match
rules pass for a source record, the matched row's values are copied to the source record.
Custom matcher tables must extend dl_matcher (e.g., 'dl_u_assignment', 'dl_u_priority').
The build will succeed if you provide an incorrect table, but the lookup will not fire on the
instance — verify the table hierarchy in sys_db_object before deploying.
OptionalmatchField pairs that determine which rows in the matcher table match the source record. Each rule compares a source table field value against the corresponding matcher table field.
Unique name for this data lookup definition. Maximum 40 characters.
OptionalprotectionControls edit/view access for other developers after the application is installed.
OptionalrunWhen true, re-runs the lookup client-side whenever any matchRules source field
changes on a form. Defaults to true.
OptionalrunWhen true, fires this lookup as a server-side business rule on record insert.
Defaults to true.
OptionalrunWhen true, fires this lookup as a server-side business rule on record update.
Defaults to false — must be explicitly enabled to fire on updates.
OptionalsetField pairs that define which matcher table field values are copied back to the source record when a matching row is found.
The table on which this lookup fires — the table whose records receive the auto-populated values.
Can be any OOB or custom table (e.g., 'incident', 'change_request', 'x_myapp_orders').
Configuration for a Data Lookup Definition (
dl_definition).A Data Lookup Definition automates field population on a source table by matching source record field values against rows in a custom matcher table (which must extend
dl_matcher), then copying matched field values back to the source record.The lookup fires as a server-side business rule on insert and/or update, and optionally client-side when watched fields change on the form.
Example