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.
Dashboard Picker is blank or it is showing the content of the correct Dashboard, but the Dashboard Picker shows a different Dashboard Name - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Dashboard Picker is blank or it is showing the content of the correct Dashboard, but the Dashboard Picker shows a different Dashboard Name
KB0748538

Dashboard Picker is blank or it is showing the content of the correct Dashboard, but the Dashboard Picker shows a different Dashboard Name


605 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

  • User has the content of the correct Dashboard, but the Dashboard Picker shows a different Dashboard Name.
  • Dashboard Picker is blank, where the Dashboard Name is empty, but it is displaying the correct Dashboard content.
  • After drilling down to a report/widget on the Dashboard and when using the browser/instance back button to go back to Ddashboard, the user experiences the issue, where the contents of the Dashboard does not match with the Dashboard Name shown in the Dashboard Picker.

Release

Upgraded from a version earlier than Istanbul to Istanbul or later.

Cause

Enabling the session debug, you will see that the user does not have read access to dashboard_w_permission database view, as per the following screenshot -

Database View: dashboard_w_permission - no read access

 

 

 

 

 

 

The ACLs evaluated and failing are pa_dashboards read ACLs. The database view dashboard_w_permission joins pa_dashboards and pa_dashboards_permissions tables.

Resolution

Starting from Istanbul, there is no need to create ACLs for database views, as the system honours the ACLs on the underlying tables. However, for upgraded instances, the admins need to create the system property glide.security.expander.view.legacy and set it to false, in order to use the new behaviour where the system honours the ACLs on the underlying tables in the database view.

Related Links

ACLs and database views [Madrid]


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.