Dashboard regarding problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-16-2023 12:15 AM
When opening a list view in a Dashboard, the header is visible. When I change the filter to 'none' (at the bottom), the header is no longer visible. If we select option other than none then also header is visible.
Is this normal behavior or some error ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-16-2023 12:22 AM
Hi @I_Das ,
I have just reproduced the error in my PDI and seems like an error from ServiceNow that the header is missing when group by none is chosen. I would recommend you to create a HI case to ServiceNow to report the problem that has encountered and to get a resolution to the issue.
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
best regards
Anders
If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.
Best regards
Anders
Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-14-2023 05:36 AM
Hi @I_Das
If my answer has helped with your question, please mark my answer as accepted solution.
Best regards
Anders
If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.
Best regards
Anders
Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-06-2023 05:53 AM
We had the same issue and I opened a ticket with ServiceNow and they confirmed there is a known problem for people discovering this. Per ServiceNow "We have verified that turning on the next experience in Vancouver upgrade causes this issue. This defect in PRB1686288 has been fixed in Vancouver Patch 5 and is scheduled to be released in the Washington DC release." When I followed the Problem it states there are 61 cases linked to this problem but it isn't on the known issues for the Vancouver patch we are on.