Schema map not displaying

daniellennon
Giga Contributor

Hi All,

First time poster, first time ServiceNow administrator. We are running;

Build: Eureka Patch6 (Prod + Dev)

Issue is affecting both instances.

Going to System Definitions > Tables & Columns and selecting for example the 'incident [incident]' table and clicking the Schema Map button opens a new tab but does not display the map. All I see is the header;

SN-Schema.png

I'm really not sure where to start troubleshooting this one. Any suggestions?

Cheers

Daniel

1 ACCEPTED SOLUTION

daniellennon
Giga Contributor

Issue resolved through the HI portal. We had a UI Script running on all forms. This script was producing error in console g_user not defined error.



Script has been disabled and cache flushed. Schema map now working.


View solution in original post

7 REPLIES 7

shawn_durrani
ServiceNow Employee
ServiceNow Employee

Have you tried any other browsers - are you getting the same result? It would be interesting to know:



  • Have you EVER been able to view the schema map?
  • What browser are you using?
  • Do you have any issues with viewing the BSM view (Configuration Management/CMDB)?  

Hi Shawn,



Thanks for the reply.



  • I'm only new, 3rd week in, it certainly didn't work on my first day. We used a 3rd party to implement ServiceNow last year, I've inquire with them but am yet to hear back. My colleague hasn't seen it work either however he wasn't aware it existed before I mentioned it...


  • I've tested on Firefox, IE and Chrome. Same behavior across them all platforms.


  • Our CMDB has a long way to mature... However the BSM map looks to be working ok, this is true in both instances

SN-BSMmap.png



Cheers


Daniel


A little more history, we started out with Dublin and upgraded to Eureka in Dec 14'.


Hi Daniel,



I've tried to replicate the the screenshot you took (albeit on a slightly new version of the platform).   It is odd that it isn't showing the table, as it forces you to select a table from the 'Tables and Columns' application.   The schema map didn't change significantly between Dublin and Eureka, so the upgrade shouldn't have caused issues.   It may be something unique about your implementation (unfortunately, hard to tell without going into the instance).



As a start, log into HI and raise an incident to get it looked at - I will ask around and see if anyone else has seen anything and get back to this thread if I learn of anything.  



ServiceNow.png