Create custom data lookups
-
- UpdatedJan 30, 2025
- 6 minutes to read
- Yokohama
- Platform Field Administration
Creating custom data lookups involves adding a lookup value, creating the definition, and activating data lookup.
Create a custom data lookup table
Create a custom table to store lookup data.
The custom table must extend the Data Lookup Matcher Rules [dl_matcher]
table. For example, this custom lookup table stores information about VIP callers and
incident assignments.
Add a data lookup value to the data lookup table
The columns of a data lookup table contain both matcher and setter field data.
About this task
Each data lookup is a query that searches for a row containing values that match the matcher fields. The data lookup then returns the value listed in the setter fields. For example, this Priority Data Lookup [dl_u_priority] table lists the combinations of impact and urgency (matcher fields) that produce a particular priority value (setter field).
Matcher fields | Setter field | |
---|---|---|
Impact | Urgency | Priority |
1 - High | 1 - High | 1 - Critical |
1 - High | 2 - Medium | 2 - High |
1 - High | 3 - Low | 3 - Moderate |
2 - Medium | 1 - High | 2 - High |
2 - Medium | 2 - Medium | 3 - Moderate |
2 - Medium | 3 - Low | 4 - Low |
3 - Low | 1 - High | 3 - Moderate |
3 - Low | 2 - Medium | 4 - Low |
3 - Low | 3 - Low | 5 - Planning |
Procedure
Create a data lookup definition record
Data lookup requires a definition record that specifies how to set one or more field values when specified conditions are met.
Before you begin
Role required: Admin
Procedure
Create a data lookup module
You can create a module for data lookup so it appears in the instance application navigator.
Troubleshooting data lookup
If the custom data lookup definition rules are not behaving as expected, check for certain conditions.
- Verify that the data lookup definition is set to run on the appropriate events.
- Verify that the matcher field is not read-only. Because users cannot change read-only fields, user interactions cannot trigger an on form change event for read-only fields.
- Verify a client script is not changing a field value. Client scripts can trigger Run on form change events even on read-only fields.
- Verify that the data in the matcher table is correct.
- If the lookup requires an exact match, verify that there is a matcher table row for each possible combination (including blank values). The lookup fails if cannot find a matching value.
- Verify that you have not created a recursive rule, such as:
If Field A = 1, then Field B =2. If Field B = 2, then Field A = 2.