Unable to attach files to the record
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2015 05:50 AM
Hi All,
In incident module we are unable to add attachment to a single record. Only for one record only we are unable to attach or remove files, for all others it is working as before.It is showing the below
Can anyone explain what will be the issue or root cause for this problem?
Thanks & Regards,
Swamy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2015 06:09 AM
Hi Swamy,
Some thoughts that may be helpful:
a) Check if you're able to save/update that record on which you want to do an attachment on. Or try to see if there's anything different with the record on which you can't do an attachment on.
b) Also, you may want to check the system property: glide.attachment.role. This property is OOB set to public, but it could be used to define which roles can create attachments.
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2015 06:27 AM
Hi Berny,
thanks for your quick reply.
1) Yes , i am able to update/save the record
2)Even for admin also it is showing as shown in the screen shot.
Only for one record it is behaving like that for all others it is fine
Regards,
Swamy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2016 07:42 PM
Hi Swamy,
I am also facing the same situation, i can't able to add attachment for only one RITM record. Can you please let me know how did you resolved that issue.
Thanks
Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2016 03:44 AM
Hi Arun,
I have resolved the issue by using below steps.
go to sys_attachment.list
search for the attachments attached to a particular request
delete all the attachments
then problem will be solved
approach2:
Rename the attachments then also this issue was resolved in my instance.
Thanks and regards,
Swamy