Tagging #IFSACH #ACHTECH
CC: @Yasas Kasthuriarachchi

HI @Lee Pinchbeck could you please check on the above since it relates to FSM.
Thanks & Best Regards,
Yasas

Hi @Kajendran Chandreswaran,

I have not seen base64 given as an accepted format but I have passed this to R&D for them to give a definitive answer on this.

Kind regards,

Lee Pinchbeck

See “WORKING WITH ATTACHMENTS AND IMAGES” starting on page 30 of the FSM6 OData REST APIs document (Help->Documentation->Integrations->FSM6 OData REST APIs.   Especially keep in mind “Note that the file/url must be accessible to the FSM server” as mentioned on page 32.

To upload binary data through OData service, we need to save the file in a location where OData service has access to read the file.

URL specified in attachment@odata.mediaEditLink should be accessible from the OData service.

E.g.

As a file URL.

POST http://<servername>/<fsmserver>/odata/attachment

{
"attachment@odata.mediaEditLink": "file://mkepde64/M5Attachments/626175160.jpg",
"attachment_id": 1209,
"attachment_name": "uploaded through odata",
"file_type": "image/jpeg"
}

As a URL.

POST http://<servername>/<fsmserver>/odata/attachment

{

"attachment@odata.mediaEditLink": "https://fsmdev64-rnd.ifsworld.com/uploads/dell_install_guide.pdf",

"attachment_name": "Attachment created through OData",

"file_type": "application/pdf"

}

When creating an attachment with an OData service hosted in Azure, we can use a fileshare created in the storage account associated with FSM server.

POST https://fsm6qa.fsm.ifsdevworld.com/odata/attachment

Body
{
"attachment@odata.mediaEditLink": "fsmshare/inbound/exceptions/000freezer.jpg",
"attachment_name": "FSMZ-2916 OData upload",
"file_type": "image/jpeg"
}

thank you for the information @sachinthaw and @Jon Reid, 

so is it possible to upload the attachment in base 64 format?

is there any acceptable encryption format that can be used for uploading attachment?