Upload file into Drop Box From NetSuite Using SuiteScript.

As noted in the other threads you found, the /2/files/upload Dropbox API endpoint is a "content-upload" style endpoint, meaning it expects the file data in the HTTPS request body. The data should be sent just as a raw octet-stream (per the "Content-Type"), without any additional encoding. (Dropbox doesn't perform any additional operations, such as encoding/decoding, on the received data before storing it.)

I can't offer help with working in NetSuite though, as it's made by a third party, but I'll be happy to help with any issues you may be having with the Dropbox API itself, but I'd need some more information. In that case, please reply with:

• the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
• the full text of any error or unexpected output

(see my below reply in response to you query for uploading PDF)

1st try 

---

Anonymous One wrote:

...

let pdfData = file.load({

                        id: 'file cabinet file id'

                    }) // this will load the file

let dataContent = pdfData.getContents() // this will fetch the content of the loaded file.

...

---

Hi Anonymous One,

Are you sure the file denoted by the id is the actual file you want to upload and not some encoded form? You can ensure it as try to save this file (dataContent) on your server local place and fetch it using ftp (or similar method). Can you open properly such a file after that?! If you cannot do it, you cannot rely that such a file will be readable on Dropbox (it's the same file).

---

Anonymous One wrote:

...

let binaryData = encode.convert({

                        string: pdfData.getContents(),

                        inputEncoding: encode.Encoding.BASE_64,

                        outputEncoding: encode.Encoding.UTF_8

                      });

...

---

As it has been mentioned already multiple times, the content you will try to upload must not be encoded in any way!!! If encoded somehow, you will get it in Dropbox encoded too. If the content is encoded in base64, transcoding it utf-8 just change one encoding to other and finally the content is still encoded (even more for binary files such encoding is destructive or can be at least). That's why such a move is incorrect definitely! For base64 encoded file you have to decode it, not transcode!!! Usually you can do it in a platform specific way (such tools are not JavaScript specific). In web browser environment, for instance, there is atob function that can do this. In nodejs, on other side, you can use Buffer class methods for the same. To be honest I'm not familiar to your environment, but there has to be something equivalent. If you don't know for such thing, ask your environment support. You can try implement such a decoding yourself if missing.

Hope this gives direction.

Hi Здравко 

I mentioned in my earlier reply I tried 2 approach.

1st - Directly uploaded the file after reading the content of the file(which worked for CSV and TEXT file but for files like PDF,DOC,ZIP etc. file was uploading but wasn't even able to open it) 

2nd - When first approach didn't work I tried to encode it (file got uploaded in DROP BOX but it was blank).

Здравко Regarding about if the file that I am loading is correct or not. I uploaded CSV and TEXT file using 1st approach it worked but for other files it didn't.

While loading the CSV file in NETSUITE default encoding for PDF and CSV file is same i.e. "UTF-8" but while uploading everything is fine with CSV but not with PDF upload.

Anonymous One, I have no idea how the situation can be explained more clear. Dropbox doesn't make difference between text based files and binary files! The content has to be uploaded as is without any change. Dropbox will save whatever you upload, as you have uploaded it, exactly (if encoded -> encoded)!!! That's why you cannot read it. Find a way to get to your files content non-encoded; it's the only way and usually there is such a way. For example CSV and TEXT files are... text!!! and that's why you are able see them, but PDF, DOC, and ZIP are not full text (in spite PDF and DOC are partially); in such files are least some binary pieces (non-representable as text), something that seems you cannot handle and as seems from your comment you're trying to pass in encoded form. All files you have passed (or will pass) in encoded form will not be readable. Do you understand the difference between text and binary file? Try to encode some ZIP file, locally on your machine, in base64 and see if this file will stay valid for the zip program you typically use. You can try transcode it to see if this helps. The same happens on your platform.

Hi Здравко ,

When I am trying to upload CSV and TEXT with same approach it is working but for PDF and other files which aren't text it is not working.

You mean for PDF I need to decode the data I am getting? 

Anonymous One, I serious doubt you don't understand the meaning of the term 'encoding'. More precisely the fact that this word meaning can vary depending on what's going work on about. Ok, I will try summarize in brief. A file is place where some data can be stored (any type of data; depending on this type, corresponding file type is assigned). Example data (and corresponding file type(s)) are text, image, archive, etc. All files (as everything digital) keep inside themself some sort on different numbers. When we're talking for text (all kind of text), file keep a sequence of number representing particular sequence of glyphs. The map that represent matching between numbers and glyps is called text encoding. All files (including text and binary) can be represented in different forms (when desirable). Their original form is called raw form. For example, if you want to ensure that particular file can be passed through a text stream, the number sequence representing file can be mapped to other sequence and vice versa. Such an example is base64 encoding. These are 2 completely different types of encodings!!! As seems you cannot make difference between and think for them as for a single thing - something erroneous!

Again, Dropbox expect the file's raw form either binary or original text encoding.

Let's hope this sheds additional light.

I run into the same issue. Any solution? 

---

yekai426 wrote:

I run into the same issue. Any solution? 

---

Hi yekai426,

Which one issue? 🤔 If you mean that you don't know how to get to raw file content (either text or other one), that's not a Dropbox API issue - ask your platform support or read their documentation. You'll get as a file whatever you provide as HTTP request body, neither more nor less (including if you put it encoded, then the file'll be encoded too in the same way). Pass the file content as is (one to one) - the only Dropbox API related requirement.

If you have some Dropbox API related question, please clarify exactly what you mean.

@Anonymous One, Have you found solution for your issue?