Problems with File Attachments
we have issues with File Attachments in both prod and test.
in prod (v9.0.6) the icon for attachments is missing, so we can view existing attachments or attach new files.
in test (v9.0.9) we have the icon, but when i attach a file and then click save i get this error:
An object of class EnterpriseManagementObject with ID 747320f4-3aa1-5e38-a3c9-66fa4946260f was not found.
Anyone know anything about this?
Best Answer
-
Shane_White Cireson Support Super IT Monkey ✭✭✭✭✭Hi @Service_Desk2,
Glad we got this fixed in the ticket but for the sake of the community here are the fixes we put in place:
1. Production was caused by your File attachments was not enabled in the Features in Admin Settings
2. Your production @mentions were not working due to your Notification Title inside your @mentions settings in Admin Settings had spaces before and after the square brackets which meant your exchange connector did not recognise the ref number and therefore created a new ticket so we changed it from [ {{Id : WorkItem}} ] to this [{{Id : WorkItem}}]
3. Your test environment was caused by what seems to be a dodgy install which you resolved by removing it all, installing 8.12.6 and then upgrading to 9.0.9
Hope this helps,
Thanks,
Shane.5
Answers
It sounds like for your prod environment you have not got the icon enables, if you go to Admin Settings > Features then enable the Header Attachments and let me know if the attachments works for this.
The icon that is not working sounds a little more tricky, did attachments normally work in the Portal before this? You could try a reinstall of the Portal and see if this fixes it.
Kind Regards,
Shane.
Glad we got this fixed in the ticket but for the sake of the community here are the fixes we put in place:
1. Production was caused by your File attachments was not enabled in the Features in Admin Settings
2. Your production @mentions were not working due to your Notification Title inside your @mentions settings in Admin Settings had spaces before and after the square brackets which meant your exchange connector did not recognise the ref number and therefore created a new ticket so we changed it from [ {{Id : WorkItem}} ] to this [{{Id : WorkItem}}]
3. Your test environment was caused by what seems to be a dodgy install which you resolved by removing it all, installing 8.12.6 and then upgrading to 9.0.9
Hope this helps,
Thanks,
Shane.