Two datalookup definitions with same matcher table

[pdom]

Hello,

We have priority data lookup defintion on incident ( Where source = Incident,           Matcher Table = dl_u_priority ) and the corresponding data lookup rule. It works perfect on incident priority lookup

However, we have same choice values as incident for impact, urgency and priority fields on problem table. So My assumption is the same priority lookup rules would work, SO i created a new datalookup definition ( where source table = problem, matcher table = dl_u_priority ). No additional lookup rules are created as the incident and problem has same field choice values

On problem table, the priority lookup is not happening. Am I doing something wrong here. Please help me to fix this issue

Thanks

[Chuck Tomasi · Accepted solution]

Personally, I would prefer to have two separate lookup tables. I don't see too many customers with the exact same definitions for impact/urgency/priority between incident and problem (and change for that matter). I fully expect at some point that you will have different definitions as your processes evolves. Having separate tables gets you ready for that time.

[Pradeep Sharma]

Hi Padmini,

You may find below link helpful.

Re: Priority auto calculation in Problem

[pdom]

Hi Pradeep,

I have done exactly samething. I have created separate data lookup definition on problem as well. But stilll not working