Table name empty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2013 06:08 PM
I have somehow created a table that has no label and no name, it shows up with the name "(empty)" in the tables list. I was trying to create a new application, didn't know what I was doing and somehow ended up with this table with no name. When I open the table to try to enter a label and name I get error messages that these values can't be changed after a table is created. There also seems to be no mechanism available (after following several documents on how to delete tables) to delete this table that has no name. I see no delete buttons, links, etc... when I'm viewing the table.
Obviously I'm a total newb to this whole ServiceNow thing and have gotten myself into a bit of a pickle. I don't even know enough the tell you all the appropriate details about the where, what and when. Sorry! Can anyone help me with getting rid of this table? I'm on the Calgary release in my dev environment so not much harm at this point but help would still be appreciated.
BTW, I put this under the documentation category here on the forum because i found no documentation of how to deal with this situation. Again, I'm new so I probably haven't looked in all the right places.
Earl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2013 09:25 AM
I did go to the created table and then to Personalize > Dictionary. That's my point. It appeared to take me somewhere different from what you described. In any case the solution is in the SN support teams hands because they need to restart the instance to resolve the problem. Thanks for your response. BTW, this is a Calgary instance.
Earl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2013 08:54 AM
You're probably using Calgary. If that's the case, report this issue to support by opening an incident.
They have documented it under PRB586617.
Regards,
/Amado Sierra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2013 09:23 AM
Amado,
You're correct, it is Calgary and I did open an incident with support. They said right now the solution is (or at least involves) to restart the instance where the problem exists. Apparently there is a fix in the works for the problem you mentioned that is due out with release 3 of Calgary. Thanks for the response.
Earl
