No matches found, when creating a data lookup definitions (scoped app)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I want Priority = Impact × Urgency to work in a scoped application, Incident table extends Task, and I want this without scripting.
Impact
Urgency
Priority
Are inherited from task table
>Created a Priority Lookup Table (Scoped App)
>Added Fields to the Lookup Table
>Populated Priority Matrix
> "While Creatig Data Lookup Definition(scoped app), Matcher table shows no matches found"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Buddy,
Data Lookup definitions arent designed to work with Task or Task-extended tables like Incident, especially from a scoped application. Even though Impact, Urgency, and Priority are inherited from Task, the data lookup framework intentionally doesn’t allow those core ITSM tables to be used as the matcher table. That’s why the matcher table list is empty.
In simple terms: Data Lookup isn’t supported for calculating Incident priority.
If your goal is “Priority = Impact × Urgency” without scripting, the supported way to do that is the out-of-the-box Priority Matrix. That logic already exists, works on Incident, and is no-code and upgrade-safe.
If you need custom behavior beyond the standard matrix, your next best no-script option is a Flow that runs when Impact or Urgency changes and sets Priority accordingly. Data Lookup just isn’t meant for this use case, and there isn’t a configuration switch that will make it work in a scoped app.
So Basically your answer is:
This behavior is expected
Data Lookup can’t be used for Incident priority
Use the OOTB Priority Matrix or a Flow instead
@NayeemSk - Please mark Accepted Solution and Thumbs Up if you found Helpful!
