Are we able to analyze and send the file size that we are sending to an endpoint?

Nextworld Platform
1

We have an endpoint for a binary file that requires a file size to be passed in. How do I configure this?

2

@ian.p let me know if this warrants a meeting or ticket for investigation.

3

Ticket created for visibility: Are we able to analyze and send the file size that we are sending to an endpoint? #437591

4

Assuming you’re talking about sending a file out of Nextword via External Endpoints (not sending the file into nextworld via an attachment endpoint), the system will automatically add a standard Content-Length header with the size of the attachment you’re sending in bytes. On the Endpoint Definition set Request Type → File, File Request Body Type → BINARY and make sure Use Chunked Encoding is unchecked. If you need to map the size somewhere else in the request, that’s not currently supported

5

This is a big blocker for us. I have created the following ticket: Unable to send file size in endpoint #437617

6

How does the API that’s being called expect to receive the file size? Header? In the body of the request?

7

In the body of the request

image (47)
image (47)1460Ă—1398 191 KB

8

OK, so that looks like it’s a call that precedes the actual call that passes the file. Is that correct? You need to determine the file’s size in advance of making the actual file-passing call.

9

Correct, sorry about not being more specific about where we are passing the value, thanks for catching that. It would be on the initialize endpoint before we send the file.

10

Sorry for the confusion, this is actually functionality we support. You can get the file size and other information for an attachment on a record via the “Loop Attachments” logic block action. You can pass this file size through to the body in your endpoint call.

image
image1142Ă—414 38.6 KB

11

Awesome! Thanks so much for the update @connor.eamon I will implement the solution.