priority matrix calculation on custom table.

niranjan314
Tera Contributor

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.

14 REPLIES 14

can you share your procedure in screenshot ? i would try in my way.


Hi niranjan314



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



The name of yours 'x_63633_serviceber_priority_lookup_custom' is probably too long.


Try and recreate the name so it's shorter, mine is 35 characters in length: 'x_tblp_incident_re_priority_lookup'



This fixed the issue for me, perhaps a limitation in the field length causes an issue somehow in the backend.


You have to add Source table & Matcher table fields to the form:


Screen Shot 2016-12-10 at 10.35.01 PM.png


Hi Michael.Fry



The fields were already added to the form (they were just hidden).


Cory CJ Wesley
Kilo Sage
Kilo Sage

There is definitely something up with this feature and Helsinki.   I was having the exact same issue with a custom table(extended from Task) and I went in and just added ONE choice to the Priority Data Lookup where I modified the Dictionary per Michael.Fry   above to point to the custom table, after that ALL of the choices started to work for that custom table.   Not just the one I modified, but ALL of them.  



Before making this change nothing was working and I can almost guarantee that was the result of making a change to the data lookup record on Incident, not the custom table, where I unchecked the 'run on form change' option as I was testing something else.   That's when all of the trouble started.   Data Lookup for Priority ceased on both this custom table and Incident at that time.  



However, even changing that value back didn't work, I had to revert the entire rule to the OOB state using the versions table and IT even told me that there was no difference when I did a compare from old(Helsinki Patch 😎 to new just to see if I was crazy.  



I'm not sure what's going on here but it's something more than just simple user error.