Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Dot walking field on "Comments and Work notes" fields show empty on list view without "Additional Comments" - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Dot walking field on "Comments and Work notes" fields show empty on list view without "Additional Comments"
KB0760384

Dot walking field on "Comments and Work notes" fields show empty on list view without "Additional Comments"


3799 Views Last updated : May 15, 2025 public Copy Permalink
KB Summary by Now Assist

Description

Dot walking field on "Comments and Work notes" fields are showing Empty on List View with out "Additional Comments" field.

Steps to Reproduce

  1. Create a new Table (i.e. "test_table").
  2. Create a new field of type -Reference (i.e. "Incident Reference") on the above table, reference to Incident.
  3. Create a record on the "test_table" showing Incident record.
  4. On the test_table, add the dot walked the below fields by Configure > List Layout:
    "Incident Reference.Comments and worknotes"
    "Incident Reference.Additional Comments"
  5. Verify comments are visible on both the added fields.
  6. Personalize the list, and remove the "Additional Comments". The column "Comments and Work notes" displays empty without the "Additional comments" fields.

Workaround

This is expected behaviour. Journal fields not stored in the table where they were referenced/defined, but in a separate table. If a journal field is dependent on other journal fields, by default there is no GlideElement defined for dependent fields, as they are not part of the display fields, so ACLs can not be evaluated.

If the dependent fields are added to the display fields, the issue is resolved. If a list view is optimized, then there is an issue, but can be solved by adding all dependent fields to the view. Turning off the system property glide.ui.list.optimize, if possible, solves the issue.

A further workaround is to set and enable to true the system property glide.script.partial_record_materializer.enabled. (see related PRB1329985/KB0793259).


Related Problem: PRB1356670

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.