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

Anandini
Tera Expert

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!

 

Anandini_0-1746007474192.png

 

Anandini_1-1746007517722.png

 

1 ACCEPTED SOLUTION

Aditya02
Tera Guru

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

8 REPLIES 8

@Anandini 

in both instances I am able to see

Ensure you add filter Trigger ID NOT EMPTY and then see if it is showing up or not

Washington DC

AnkurBawiskar_0-1746170126624.png

 

In Yokohama also I am able to see

AnkurBawiskar_1-1746170434789.png

 

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

Aditya02
Tera Guru

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

@Anandini @Aditya02 

I was able to add that on Yokohama instance.

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

hello @Ankur Bawiskar ,

 

Actually We also faced the same situation for our custom tables. We have raised High ticket as well. This solution is provided by the Servicenow team.

 

Thanks & Regards,

Aditya