Hi!
I am doing a process flow in order to set up OneDrive API file upload.
The thing is that I used Web Connection in the call to receive the token and also in other calls where I tried doing the upload by pieces with a session.
In the end, the option was to do it in ”one go”, without splitting up the file in order to upload it.
The problem is basically that when I am doing the call to upload the file with Web Connection, the call is done but the resulted file is corrupted.
When I am doing the same call with Http Connector the resulted file is without any problem.
Is something that I am missing or the file that I am passing through parameter is getting modified and that results the corruption of the file?
The setup done in Http Connector:
![](https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/f5fbd040-6f74-4148-a32b-5282a3281eee.png)
The Setup from Web Connection:
![](https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/a145bcfe-cb3b-4fad-a0e4-e06f633e4714.png)
![](https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/da4d9f49-058a-46a9-a45c-ba9df9da4205.png)
Those are the endpoint parameters, there by the way, I tried for bodyContent different pre-processing (Auto, None, Base64) none of them changed the result.
![](https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/d61f92e0-69af-4836-af38-49c9de2c6c09.png)
And the input for the Web Connection parameters:
![](https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/12a0a949-066b-4112-bb6d-c18656c18ad6.png)
As a mention, storage is varbinary_max, anyway, as I said, is very strange that with Http Connector works perfect and with Web Connector not.
If you have ideas what is the reason for that or what I am skipping please leave a comment, thanks!
Best answer by Mark Jongeling
View original