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]

Hi Padmini,

I don't know if this is supported or not. You can verify this is (or is not working) by using the field watcher. Right click on the priority field and select Watch priority.

Now as you change impact and urgency, observe the changes in the window below (you may have to switch to Medium mode on the left to see the transcript.)

Field Watcher - ServiceNow Wiki

[pdom]

Hi Tomasi,

Thanks for your quick response. I have done what you said above and looks like no datalookup is being triggered?

When I have repeated the above steps on incident, I could see the datalookup triggered but on problem.

IS there any issue going here? Any solution to get this working ? Please help

Thanks

[Chuck Tomasi]

That would indicate that shared tables are not supported and you will have to create a new one for priority.

[pdom]

HI Tomasi,

Looking at the post mentioned by pradeep, some one got this working by having two data lookup definitions. Do you think if this is a specific servicenow version issue?