How to replicate the IFS Cloud file upload flow as performed by the backoffice?

Flow Connect
1

Hi everyone,

I’m working on a Novacura Flow that uploads physical files to documents in IFS Cloud using the DocReferenceObjectAttachmentHandling.svc projection. The document creation works fine, but when I try to PATCH the /FileData endpoint to upload the binary, I consistently receive a 428 Precondition Required error.

I’ve noticed that the IFS backoffice performs several steps before the file upload succeeds, including:

  • ValidateClassAndFormat

  • CheckRepositoryIsValid

  • GetEditableLuName

  • GetAttachmentCount

  • DocReferenceObjectResultSetOrderBy

  • GET /EdmFileReferenceArray(...)?$select=FileData

  • Then finally, the PATCH /FileData call

My question is: Is it necessary to replicate all these steps in Flow to make the upload work? Or is there a specific call or condition that enables the file reference so that the PATCH succeeds?

I’ve tried encoding the filename in Base64 URL-safe format and setting CreateFileRef = TRUE, but the error persists. I’d really appreciate any insights or examples from others who have successfully implemented this flow.

Thanks in advance!

main/ifsapplications/projection/v1/DocReferenceObjectAttachmentHandling.svc/DocReferenceObjectSet(DocClass='PDF',DocNo='1004941',DocSheet='1',DocRev='A1',LuName='CustomerInfo',KeyRef='CUSTOMER_ID=100029^')/EdmFileReferenceArray(DocClass='PDF',DocNo='1004941',DocSheet='1',DocRev='A1',DocType='ORIGINAL',FileNo=1)/FileData
Sent: 08/10/2025 01:06:38 p. m. -05:00
Headers: 
	X-IFS-Content-Disposition:filename=RG9jdW1lbnRvIGRlIENyZWRpdG8gcG9yIE5PVkFDVVJB
	Content-Type:application/octet-stream
	Authorization:Bearer *****
2

Check out this example: Hub - Flow Connect

2 Likes