priority matrix calculation on custom table.

[niranjan314]

Hi guys,

I have currently made one simple custom application and in that application i have created one custom table. So in that custom table i have added some fields and i have added Impact, urgency and priority field same as in incident table. But i am not able to calculate the priority matrix on my custom table same which calculated in incident table. please kindly suggest me a solution.

[Michael Fry1]

I suppose you'll need to recreate the lookup rules since the rule choices are coming from the Incident table. Then you can create a new definition.

[niranjan314]

Since i have recreate the lookup rules same as which was previously created priority lookup by extending data lookup matcher rule table. but the thing is no value is populating in source table field.

1. i have created same priority lookup custom same as priority data lookup by extending data lookp matcher rule.

2. i have added that table into data lookup definition.

3. in that table i have added records same as priority lookups

4. after clicking on new button on matchers field definition the values are not populating in matcher table field.

now where i am making the mistake that i am not able to find. i hope u will understand by above screenshots.

[Michael Fry1]

Section 2 provides the steps to create a custom lookup: http://wiki.servicenow.com/index.php?title=Data_Lookup_and_Record_Matching_Support#gsc.tab=0

On your priority lookup rules, just confirming your choices are coming from your custom table.

[Francis Twyman]

Hi niranjan314,

I have exactly the same issue, we're running on Helsinki Patch 4.

Did you ever find a solution to this problem?

My choices on the lookup table are coming from my custom table as Michael.Fry has suggested, however on the Data Lookup definition I cannot select fields in the matcher table,.

My application is its own custom scope.

Any advice?

Thanks

[Francis Twyman]

Update:

I recreated my lookup table with a shorter name and it worked.

The application scope name that gets added to the front made the table name too long.

A-OK now.