- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2023 05:18 AM - edited ‎11-06-2023 05:29 AM
I've found that in all of our instances (a Dev, Test, and Prod), none of the Change Task forms are correctly showing the parent Change Request number in the "Change Request" field. The records are correctly linking, as the field has the "i" icon which brings up the correct Change Request, as well as the parent record having the Change Task in the Related List > Change Task list.
I have also confirmed that the Change Request > Number field is set up as the Display field for the table, and that there does not appear to be any ACLs in place that should limit the readability of the field (I am an admin, so the Admin override should also kick in if this were the cause). The numbers appear correctly on the Change Request List view, it is only in the Change Task form/list view that the number field is not showing correctly.
SOLVED: I found the issue was that there were 2 fields set as the "Display" field for the table. I thought I'd tested this previously, but when more carefully adjusting the fields this morning, I was able to get the correct information to show.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2023 05:31 AM
Hey Atulya, I found that the issue was actually just due to there being more than 1 field set up as the "Display" field (got to love those headscratchers with simple solutions). Thank you for the insight!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2023 05:24 AM
Greetings!!
Just to know, are these task created manually or via flow / workflow?
Did you check any client script / UI policy running on this? ( Chance are less but still check)
Is any other available role facing this issue?
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2023 05:31 AM
Hey Atulya, I found that the issue was actually just due to there being more than 1 field set up as the "Display" field (got to love those headscratchers with simple solutions). Thank you for the insight!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2023 05:39 AM
God to know @ZachFunderburk
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-15-2025 12:30 AM
Hi @ZachFunderburk ,
Did you come to know the root cause of this and why did it happen in the first place?