How to use CreateAndImportDocument projection via REST (Postman) to attach a file to a Purchase Requisition?

Hi all,

I'm trying to attach a file (PDF) to a Purchase Requisition through REST APIs in IFS Apps 10, using Postman for manual testing before moving to code. I've identified CreateAndImportDocument.svc as the right projection (confirmed by inspecting Aurena's network traffic), but I'm stuck on the file upload step.

What works so far:

Calling the CreateDocument action successfully creates a document header:

POST {baseUrl}/CreateAndImportDocument.svc/CreateDocument
Content-Type: application/json

{
  "DocClass": "900",
  "Title": "Test Attachment",
  "CreateFileRef": "TRUE"
}

Response returns the new keys:

json

{
  "DocClass": "900",
  "DocNo": "1000109",
  "DocSheet": "1",
  "DocRev": "A1"
}

Where I'm stuck:

After creation, querying EdmFileSet for the new document returns an empty array:

GET {baseUrl}/CreateAndImportDocument.svc/EdmFileSet?$filter=DocNo eq '1000109' and DocClass eq '900'
→ { "value": [] }

I tried several values for CreateFileRef (TRUE, true, Y, 1, a filename) — none of them produced a file slot. I also tried POST directly to EdmFileSet to create the file entry manually, but got 404.

My questions:

1. What is the correct value/format for the CreateFileRef parameter in CreateDocument? Is it a boolean-as-string, a filename, or something else?
2. After CreateDocument, what is the exact sequence of REST calls needed to upload the binary file content? Specifically:
   • Should the EdmFile entity be created via POST to EdmFileSet, or is it expected to be auto-created by CreateDocument?
   • Is the binary uploaded via PUT to the FileData stream property, or via a bound action like EdmFile_StartCheckIn / EdmFile_FinishCheckIn?
3. Are there specific permission sets required beyond standard document read access (e.g., DocMan Advanced) that could cause file slot creation to silently fail without returning an error?
4. Finally, for connecting the document to a Purchase Requisition via ConnectObject, what is the correct LuName and KeyRef format for a PR header (and a PR line, if different)?

A minimal end-to-end Postman example (request URLs, headers, bodies in order) would be hugely appreciated — even a screenshot of Aurena's network trace during a manual file attachment would help me reverse-engineer the rest.

Authentication is Basic Auth, IFS Apps 10 Release 14 on-premise.

Thanks in advance!