GlideRecord.setTableName - empty table name On Workflow?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-04-2017 10:43 PM
I have a catalog item with a workflow associated with it. The workflow acts on the sc_req_item table.
Whenever I order the item from my Service Portal, the following error appears in the log, and the workflow doesn't appear to run.
Does anyone have any clues where I should start with trying to solve this? I can't see anything wrong with the way things are set up.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-04-2017 11:05 PM
Hi Steve,
I think there are some evaluator script in service portal and in you case you have made some changes to some widget in service portal and causing this issue. Check the logs for error message contains GlideRecord.setTableName and check for the source of that log. You will get an idea of this issue.
Hope this helps.
Regards
Ujjawal

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2017 03:59 PM
Not sure what you mean. The messages in the error log that contain "GlideRecord.setTableName" are the one shown above with a source of com.glide.ui.ServletErrorListener. There's no other information other than what you see in my screenshot.
One of these errors generates everytime I order a product. The only thing I've been working on is the workflows, so I assume it has something to do with them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2017 07:28 AM
Am facing the same issue , did this issue was resolved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2017 11:43 PM
In Jakarta this log entry is written when opening a Record producer from the Service portal.
I have confirmed it in both a Customer instance and a developer instance running Jakarta.
Anyone know if theres a problem related to this ?
OOB dev instance -> open "Report an issue" and this log i written