The CreatorCon Call for Content is officially open! Get started here.

Made a field hidden on task table, but now it is not reportable, why would that happen?

snow_beginner
Mega Guru

Hi, so there is a field 'Escalation Reason' which is a drop down field with 7 choices. It is present on the incident_task table and when a user escalates an incident, the value is captured in that field.

 

The ask was to make it a hidden field but still it should capture data and be reportable. I made it hidden by using the slush bucket in the form layout and moving it to the left side. However, now when a report is run, the reason is not captured. How can I fix this. Attached is a screen shot of the issue

 

Screenshot 2024-01-02 143105.png

 

So looking at the graph, this field was created in May last year and all the lines (blue colors) represent the escalation reasons for each of the month when it this report was run. The person ran it today (in January) and there is no data for the escalation reason (no blue line - he chose the reason as customer impacting). Why is this happening? How can I fix it?

2 ACCEPTED SOLUTIONS

Hi @snow_beginner 

 

The reason can be data is so small ad ranges are more , so it is look like No line.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

Kristen Ankeny
Kilo Sage

I'm noticing that the key shows "Incident Escalation Reason" and the list view shows the "Reason for Escalation" - is the Incident Escalation Reason populated?

View solution in original post

14 REPLIES 14

I agree with this - I don't think it's not being reported, but 3/100 is such a small number it looks low. Can you copy the report and limit to just the current month to see if the scale changes and shows you the line is not at 0.

Hi, the issue is not that there isn't a line. There is a line and I can see it if I zoom in to it. The issue is that the reason for escalation is coming up empty rather than one of the choices. 

 

Choices for reason for escalation:

pic-9.png

 

graph showing 1 of the choices in october

picture-3.png

 

graph of January - showing there are 3 escalation tasks but not showing the choice for them, showing it as empty.

picture-4.png

 

even though for all 3 tasks there is a choice selected

picture-5.png

 

thats the issue. I did replicate the report in dev and set the filter to this month only and it was happening in the same way. it was showing the tasks but not the reason for them. Could the filter be the problem:

 

report filter:

pic-5.png

Hi @snow_beginner ,

Just to confirm, does this record should be visible on the report (Can it pass the report filter conditions?)? As field's value is visible on the list, it should be visible in the report if there isn't any restriction (i.e. ACL) for report viewer. 

Kristen Ankeny
Kilo Sage

I'm noticing that the key shows "Incident Escalation Reason" and the list view shows the "Reason for Escalation" - is the Incident Escalation Reason populated?

Thanks for pointing that out, it was the issue.