Data Lookup not working for extended Incident table in Scoped App

[korerishikesh]

Hi everyone,

I’m working on a ServiceNow implementation in a scoped application where I created a custom table that extends the Incident table.
My goal is to automatically populate Priority based on Impact and Urgency using a Data Lookup Definition.

What I have done so far

• Created a scoped app

• Created a custom table extending Incident

• Verified inherited fields (impact, urgency, priority) exist on the form

• Created a custom matcher table extending "dl_matcher"

• Added fields Impact, Urgency, Priority to the matcher table

• Added matrix records for all combinations

---

Issues I am facing

1️⃣ When configuring Choice Table for matcher fields:

• My scoped incident table does not appear in the list

• Even though it extends Incident and has the same fields

• I understand it inherits choices from Task/Incident, but I’m unsure what the correct choice source should be

2️⃣ While creating the Data Lookup Definition:

• Source table = my extended incident table (works fine)

• Matcher table = my custom matcher table (visible only after extending dl_matcher)

• However, lookup is still not auto-setting priority on the form

3️⃣ I am unsure whether:

• I should reuse Task/Incident choices for matcher fields

• Or create independent choice values in matcher table

• Or use integer fields instead

---

What I want to achieve

Automatically set Priority based on Impact + Urgency for records created on my extended Incident table inside a scoped app, using a configuration-driven approach (Data Lookup).