- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2017 01:14 PM
We have a Catalog Item that allows a user to download file from the sys_attachment table, complete, and attach back prior to submitting. The spreadsheet can be downloaded and *seemingly* attached to the record prior to submitting. Immediately after hitting the Submit button, a white screen appears with "Requested Attachment Does Not exist"
Despite this "error", the RITM record does contain the attachment. While the end result is providing the intended result with the file, the message of "Requested Attachment Does Not Exist" visible to the end user is not acceptable.
Here is link to access spreadsheet:
I complete the spreadsheet and save back to my desktop. I then attach to the catalog item before submitting
After I click Submit:
I found this older discussion at Attachments are missing but it did not provide the details I need. Any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2017 10:31 AM
I opened a HI case on this and was informed it is a know issue and set to be fixed in a future release (KINGSTON). As a workaround, we configured the link to open the Excel template in a new tab. We accomplished this by modifying the Widget to include target="_blank".
This resulted in a split-second jump to a new browser tab, but it quickly returned to the main one allowing the form to be completed and submitted.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2017 12:49 PM
Not sure I followed completely. Can you just redirect to the RITM created? Doing so I would bet you won't see the message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2017 07:37 AM
I would be willing to give that a go as It would be better that a error. I am not a scripter/developer nor do I know where that would be completed. An online search suggested modifying the SC CAT ITEM widget, but we don't want a redirect on all Items.
The preferable landing page would be like the image below.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2017 09:35 AM
Just to confirm this IS a catalog item and not a Record Producer? If it's a cat item, something must be redirecting it otherwise you'd end up on the RITM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2017 11:21 AM
It is a Catalog Item. My theory of what it is redirecting is the "software order..." link in the image below. This link is tied to a file on the sys_attachment table. Upon clicking this link, the URL does change from
"...service-now.com/it?id=sc_cat_item&sys_id=b47b43dddb7543c0844bd79b5e961951"
to
"...service-now.com/sys_attachment.do?sys_id=c9d41e91db86c700844bd79b5e9619b8"
Despite this URL change, the view onscreen remains the same. I then complete and add the attachment to the record before submitting. When I submit, the URL then changes to:
"...service-now.com/sys_attachment.do?id=ticket&table=sc_req_item&sys_id=a1cfa609dbda4340844bd79b5e96190... [This sys_id is that of the created RITM] This is the URL that displays the "Requested Attachment Does Not exist."
If I change the above URL to ""...service-now.com/it?id=ticket&table=sc_req_item&sys_id=a1cfa609dbda4340844bd79b5e96190b [replaced sys...
the correct page appears.
Somehow, utilizing that "software order" link to the sys_attachment table disrupts the URL. It is important to not that this worked last week. The defect was noticed Friday November 3rd. Could it be coincidence that Instanbul Patch 9 was installed on November 1st and this was noticed after that?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2017 11:44 AM
Could be tied to Patch 9, but just don't really know as I can't see the whole picture. I think at this point a call to HI support is the place to go. They can access your instance and see what's going on