I am using the 'setBinaryData' REST method to add documents to existing records in Rollbase.
If you look at the login method, you can choose whether you want to use the HTTP header parameters or the URL parameters. Am I limited to the URL parameters when using setBinaryData? Because I am trying to send a binary64 in the URL header to a file upload field, but the value is not picked up by Rollbase.
The only result I am getting back is:
Msg: 'Field "document" has been cleared on <recordname>'
The new value is never assigned to the file upload field.
As it turned out I forgot to add the 'contentType' header. After setting that to 'application/octet-stream', I was able to upload my documents just fine and open them from Rollbase.
As it turns out, I forgot to add the 'contentType' header.
After adding that, I was able to upload the documents to existing records in Rollbase.
As it turned out I forgot to add the 'contentType' header. After setting that to 'application/octet-stream', I was able to upload my documents just fine and open them from Rollbase.
As it turns out, I forgot to add the 'contentType' header.
After adding that, I was able to upload the documents to existing records in Rollbase.