Can't display this dashboard - Workspace

joaojunior
Tera Contributor

Dear community,

 

I've a custom Workspace with a dashboard embedded in the homepage, which was working normally but without any modification from my side, is not displaying anymore. I'm getting this message now:

error1.png

 

 

Although my configuration is the same as before, and I can find normally my dashboard

 

error2.png

 

I can also normally find my dashboard record in "Dashboards" and all permissions regarding users and role sharing remains exactly the same.

 

Something that I noticed is my instance was upgraded from "glide-xanadu-07-02-2024__patch4-11-22-2024_12-02-2024_1408.zip" to "glide-xanadu-07-02-2024__patch5-12-24-2024_12-31-2024_0455.zip" a couple hours ago. This upgrade action was done in 2 of my instances, and one of them I was not touching for even longer, but now I got the same type of error.

 

Any type of recommendation to have at least make a workaround? (I already trigger a ticket so ServiceNow support)

 

29 REPLIES 29

Heyy Susan,

 

Thanks for the info.

Requesting if you could share with us the inputs from support whenever you receive. Meanwhile I too raised a case so that this issue gets highlighted. 

 

Hi @Arnab Dey1 - We received this update from SrviceNow Support. We'll upgrade the plugin next week to see if it works.

 

...the logs are related to a known defect: PRB1825127 and has been addressed in SOW 7.0 and has also been backported to SOW 6.1.5, which is supported for Xanadu. The fix will be available to customers on March 12.

Once the fix is available, you can update SOW (sn_sow) to this version , so you will not be issues further.


Susan Williams, Lexmark

Oh Super Thanks Susan for your efforts to revisit this thread. 

This looks positive. So will wait for the day. 

Our case is still getting investigated. I did though informed the assignee about the prb you provided.

 

Just a hint of our work: We are building a custom workspace for some of our customers. This will be further extended to all our customers as a generic workspace. I hadn't had any work experience with workspace or UIB. I started learning from scratch just a couple of months back. It has been really tough for me. 

But yes people like you and the rest of community gives the much needed oxygen from time to time. 

Happy Friday and the weekend.

 

Many Thanks,

Arnab

Regarding the PRB and plugin upgrade that was supposed to fix this... we upgraded the plugin to 6.1.5 today and this issue is still occurring. We will update our case with this info to see what ServiceNow Support has to say about it.

 

Here's a specific example: 
  1. Today, I viewed a project in Project Workspace and opened its Analytics. The dashboard displayed correctly.
  2. Then I viewed the Vulnerability Manager Workspace and clicked on its Dashboards. The "Project Summary - Scrum" dashboard was displayed. This is the dashboard I had previously viewed in the Project Workspace. And there are no VR related dashboards available via the dashboard picker. They are all project related dashboards.
  3. Then I viewed the Service Operations Workspace and clicked on the AIOps Dashboards. I got this message: Can't display this dashboard, The dashboard that you are looking for was not found
  4. Then I viewed the Security Incident Response Workspace and clicked on the SIR Dashboards and selected the MITRE ATT&CK dashboard. The dashboard viewed correctly. 
  5. Then I viewed the IT Remediation Workspace and clicked on the Dashboards. I got this message: Can't display this dashboard, The dashboard that you are looking for was not found.
  6. After all of the above, I went back to the Vulnerability Manager Workspace and clicked on its Dashboards. Previously, the "Project Summary - Scrum" dashboard was displayed. But this time, I got this message: Can't display this dashboard, The dashboard that you are looking for was not found.

Susan Williams, Lexmark

Thanks for the update Susan.

We are even struggling to make the case assignee understand the issue on the first place. They are still trying to reproduce the issue in a temp instance.

I will have further updates soon.