Timing of storing attachment text extraction from binary stream

Nextworld Platform
1

Is it true that attachments added via endpoint response are only text extracted at the end of a transaction? Using NATE resulting at end of boundary but not maintained during mapping such as a LB designated to run in a new transaction. When NATE is NOT is use, only at the end of the call stack.

I have a working solution but it seems convoluted and our ideal would not be to have to use NATE for a workflow transaction.

My goal is to use an intelligence model to classify the an attachment type. I’m using a External Endpoint Call to locate a file which is located on an external record. In this case a GitHub Repo, but I don’t think the location is important but rather when the Endpoint successfully retrieves the attachment it uses the “Record to Add Attachment To” on the Call External Endpoint Action it retrieves as binary stream. These actions are all part of 1 workflow Conditional Logic Block.

When I have NATE Off. I am able to retrieve the attachment (Successful Endpoint Call logged) but when the record is passed to the Model it errors saying the attachment provided is unsupported. In my test case, I know the document type is supported and can manually upload directly and execute the same intelligence API as a 2 step process to success.

With NATE ON, I am able to retrieve the attachment (Successful Endpoint Call logged) but when the record is passed to the model. It says no attachment was provided.

I was able to get a working project by turning NATE on and using a LB called in its own transaction boundary to make the endpoint call. The caveat being I had to re-fetch the record to get the model to recognize the attachment is on the record back in the original boundary. I could not set DSN from the LB output or any other value to identify this as would normally be the case when a record is fully updated in another boundary.

Am I stuck with the timing of when NW processes the attachment and converts binary stream to extracted text? Is there a way I could have forced extracted text from my endpoint?

NATE ON, New Transaction Boundary and refetch all seem like they shouldn’t be necessary

2

Hey Aaron!

Everything I’m seeing suggests that the behavior you’re experiencing is a bug.

NATE vs non-NATE should not affect the format (nor parse timing) of the attachment created via External Endpoint. As far as I can tell, we always parse those results as Text or JSON right away and will always have the response in the same format by the time the “Call External Endpoint” action finishes. There may be some difference with when we upload that attachment to our attachment data store, which would explain why you had to re-fetch/use a new transaction w NATE, but that shouldn’t impact the attachment type at all.

I can’t see any reason that the attachment would be in a different format with/without NATE. Please file a bug with as many details as you can include (ideally replication steps) and we’ll get it investigated.