Error Message when I open Service Portal Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2017 04:40 AM
Hi All:
When I open the Service Portal Page I'm getting the following Error Message:
org.mozilla.javascript.EvaluatorException: GlideRecord.setTableName - empty table name (; line 58)
Script source code logged to console
Failing widget: 'Header Menu' (5ef595c1cb12020000f8d856634c9c6e) called from: 'Stock Header ' (bf5ec2f2cb10120000f8d856634c9c0c)
Please if you can help me to solve this issue. I tried to search it and I found that it's related to Service Portal -> Widget -> Header Menu but I couldn't do anythig.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2017 08:36 AM
Hi,
Usually this error occurs when you try to create a GlideRecord instance with a empty table name, for example, var gr=new GlideRecord('').
I ´ve seen my Header Menu widget but I have not found anything that could causes that error.
Did you customize the widget or you ´re using the default version ? What ´s your instance version ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2017 09:31 PM
So please can you tell me how can I fix. wehre should I go in the system to fix this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2023 11:36 PM - edited ‎09-26-2023 11:40 PM
Hi,
I had similar kind of errors for specific users on Portal side.
The Reason behind is there are an approvals which are in requested state for that user & having approval for field as blank.
When I remove/approve that approvals from approval table then it work fine & errors are not appeared.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2017 04:52 PM
I had the same problem and it was caused by a sysapproval_approver record i managed to created that did not have value in the document_id field. Once I fixed this the problem went away.