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.
Extended fields not appearing after expanding another table in slushbucket - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Extended fields not appearing after expanding another table in slushbucket
KB0564212

Extended fields not appearing after expanding another table in slushbucket


2023 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

On a slushbucket, after the reference fields are expanded by clicking on the [+] sign, the extended fields no longer appear towards the end of the list in the slushbucket.

Steps to Reproduce

  1. Ensure that the property glide.ui.list.allow_extended_fields is set to true.
  2. Navigate to Incidents > Open.
  3. Open any incident record.
  4. Right-click on the header and select Personalize> Form Layout.
  5. Scroll to the bottom of the list to check that the extended fields are listed.
  6. From the Available slushbucket, select Assigned to.
  7. Click on the [+].
    This would take you to another list of fields.
  8. Navigate back to the original list by clicking on Incident Fields.
    Note that the extended fields are no longer listed in the available slushbucket list.

Workaround

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem please contact ServiceNow Technical Support


Related Problem: PRB629519

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.