Using the Get File OneDrive module and specifying a file to retrieve and upload to AirParser, I was getting incomplete uploads. Latenode would receive a HTTP 201 indicating a successful upload, but AirParser never completed parsing the PDF that was uploaded. When I download the preview of the file in the Get File module, the file opens correctly and appears intact.
To test the my theory that it appears to be passing incomplete file contents to the AirParser module, I added a Create Text File OneDrive module and had it read out the file contents to a text file and I then ran them through a base64 decoder. The header of the PDF is there, but none of the file contents are included. The entirety of the contents of the base64 encoded PDF are: JVBERi0xLjcNCiX+7f7tDQoxMyAwIG9iag0KPDwNCi9UeXBlIC9QYWdlDQovUGFyZW50IDMgMCBSDQovUmVzb3VyY2VzDQo8PA0KL1hPYmplY3QgPDwgL2ltMSAxNSAwIFIgPg== which decodes to: %PDF-1.7 %þíþí 13 0 obj << /Type /Page /Parent 3 0 R /Resources << /XObject << /im1 15 0 R >
If you copied the content of the “Content” section, it won’t display correctly because it’s only a preview of the file, represented as a base64 string that includes the first 100 characters.
Could you please share a link to the unsuccessful execution? I’d like to understand the issue better
No, instead of having the content section be uploaded to AirParser I had it go in the body of the text file so I could see what it was doing as I’m not aware of any way to view the actual execution results. When you view the output of a module it just shows the {{$1.body…}}.
Here is a link to the scenario where I had it create the text file: Latenode
Having a similar problem myself when trying to get onedrive file content of a pdf file for s3 upload in next node. If I have it as a base64 it uploads a truncated file 105byte file with first 100 characters. If classified as binary file , it does not find it. Has their been any fix or solution for this?
Hi, could you please share an example of your issue with a screenshot or screencast?
It’s very likely that the confusion is coming from the fact that you’re referring to the file’s “content” as base64, when in reality it’s a variable containing the binary file.
(This is likely because the name includes the first 100 characters of the base64 string, which can be misleading.)