a month ago
Hi SnapLogic Community,
I'm currently migrating pipelines from the legacy REST POST Snap to the new HTTP Client Snap, specifically for uploading files to SharePoint using the REST API.
While trying to replicate the behavior of the old POST Snap, I'm facing issues where the file is uploaded, but it's not readable in SharePoint.
We used the "content" field directly in the HTTP entity.
The file was uploaded and could be opened properly (PDF, CSV, etc.).
Following the guide here:
🔗 https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/3872063490/Migrating+from+REST+Snaps+to+HT...
Set Method to POST
Used raw as HTTP entity type
Sent file content using $content or even the full binary from a Binary to Document Snap
➡️ Result: The file is uploaded, but the content is corrupted/unreadable.
The only thing that worked so far is:
Writing the file to the SnapLogic file system
This uploads a readable file to SharePoint, but I’m concerned this may not scale well for files larger than 100MB or in more dynamic scenarios.
I'd really appreciate any insight on:
Why this difference exists between the two Snaps
If there's a clean solution using only the HTTP Client Snap
Whether there's a reliable way to send raw binary content without fallback to SnapLogic file storage
Thank you!
3 weeks ago
Hi @mzagar ,
If you are reworking the flows, why don't you use https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1151729711/SharePoint+Online+-+Upload+File