Why is trigger_id not showing in the list view of asmt_assessment_instance_question table?

Anandini · ‎04-30-2025

Hello Everyone,

I’m facing an issue in ServiceNow related to referencing fields across tables.

In the asmt_assessment_instance_question table, there's a reference field called instance that points to the asmt_assessment_instance table. In the asmt_assessment_instance table, there is another reference field called trigger_id, which points to my custom table u_cg_payroll.

Now, when I open the form view of a record in the asmt_assessment_instance_question table, I’m able to see the trigger_id field (via the reference to instance.trigger_id) without any problem. However, when I try to display the same trigger_id in the list view of the asmt_assessment_instance_question table, it doesn't show up — even if I add instance.trigger_id as a column.

Does anyone know why this happens or how to make instance.trigger_id visible in the list view?

Thanks in advance for your help!

Aditya02 · ‎05-05-2025

Hello @Anandini ,

If the field "Trigger ID" is not a reference field, but rather a Document ID type field it work as you expected.
By design, Document ID fields cannot be dot-walked or used for display/filtering via dot-walking. This is a platform limitation.

📘 Please refer to the official documentation for more details:
🔗 Document ID field behavior – KB0860526

As you mentioned the current behavior is as expected starting from the Xanadu/Yokohama release.
Prior to Xanadu, the behavior was different due to how ACLs were handled. With the significant enhancements introduced in the Xanadu release, this change became noticeable post-upgrade.

I have compiled the relevant documentation for your review:

🔗 Access Management Release Notes – Changes in Xanadu:
https://www.servicenow.com/docs/bundle/xanadu-release-notes/page/release-notes/now-platform-security...

Although you want to display the record in list view you must follow this:

To allow record data to be displayed as expected, you can enable the system property:
glide.script.partial_record_materializer.enabled = true

✅ If this helped, please mark it as the answer and hit the thumbs-up to help others find it too!

Regards,

Aditya

View solution in original post

Ankur Bawiskar · ‎04-30-2025

@Anandini

trigger_id is a document id field and not simple reference field

So it won't work and show in list view as per your expectation

I tried the same and it didn't work for me as well

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

Anandini · ‎05-01-2025

hello @Ankur Bawiskar ,

I’m able to get the ID in the asmt_assessment_instance table, but this issue only started occurring after we upgraded our instance to Yokohama. The same problem is happening with another table as well, which was custom-created.

Ankur Bawiskar · ‎05-01-2025

@Anandini

I tried in Yokohama and it didn't work

Will check in other instance tomorrow and share the update.

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

Anandini · ‎05-01-2025

hello @Ankur Bawiskar ,

Did you found anything..