[Bug] SharePointService.CreateFile() only work with text value file content

[emibanana]

Describe the bug

SharePointService.CreateFile via the @microsoft/power-apps SDK saves corrupted or non-binary file content to SharePoint when uploading images. The file is not openable by any image viewer.

Steps to Reproduce

try upload a photos using CreateFile(dataset: string, folderPath: string, name: string, body: string, queryParametersSingleEncoded?: boolean) where no matter what passed into the body parameters it will always end up corrupted, becoming pure text value

Expected behavior

A valid binary image file (JPEG/PNG) is saved to the target SharePoint document library folder and is openable by any image viewer.

Actual behavior

The uploaded file contains corrupted content. Three variations were observed depending on how the body parameter was prepared:

Body passed to CreateFile	File content saved to SharePoint
JSON.stringify({ $content-type, $content })	"{\"$content-type\":\"image/png\",\"$content\":\"iVB...\"}" — double-serialised JSON string including outer quotes
Plain object { $content-type, $content }	{"$content-type":"image/png","$content":"iVB..."} — JSON envelope object stored as text
Raw base64 string	"iVBORw0KGgo..." — base64 ASCII text stored instead of binary bytes

In all cases the connector operation CreateFile stores text in the file rather than decoding to binary bytes.

Screenshots or Error Messages

you wont need a screenshot to understand this

Environment information

• Framework / build tool: React 19, Vite 7, TypeScript (strict)
• SDK: @microsoft/power-apps (Power Apps Code App)
• Connection: SharePoint Online connector (shared_sharepointonline)
• Operation: SharePointService.CreateFile(dataset, folderPath, name, body)
• Schema: body is declared "in": "body", "format": "binary", "type": "string" in the connector OpenAPI schema

Additional context

Root cause traced through SDK source:

1. ConnectorDataOperationExecutor._buildOperationBodyParam calls JSON.stringify(params[bodyParam.name]) on the body value regardless of the parameter's format field
2. The result is passed to retrieveDataAsync, which wraps it in new Blob([body], { type: 'application/json' }) and sends to the Power Platform gateway
3. The gateway forwards the JSON-encoded string body to the SharePoint REST API endpoint (POST /{connectionId}/datasets/{dataset}/files)
4. SharePoint stores the received text payload verbatim instead of binary image bytes

The SDK does not special-case format: binary body parameters in connector operations — it always JSON-serialises them. A native binary/octet-stream passthrough path (uploadDataAsync) exists in runtimeDataClient but is only wired up for Dataverse file column uploads, not connector operations.

[emibanana]

Now here is the fixed up version of your SDK, youre welcomed.

node_modules@microsoft\power-apps\dist\internal\data\core\data\executors\connectorDataOperationExecutor.js

and

node_modules@microsoft\power-apps\dist\internal\data\core\runtimeClient\runtimeDataClient.js

connectorDataOperationExecutor.js
runtimeDataClient.js

[eschavez]

Thanks for the thorough root-cause analysis - your diagnosis is exactly right. The SDK's connector operation executor always JSON-serializes body parameters without checking the format: binary field, which is what causes the file content to arrive at SharePoint as text instead of binary bytes.

This is a known issue we're tracking here: #230 - Connector operations with format: "binary" body parameters upload corrupted files

A fix is rolling out. The SharePoint CreateFile case you've described is covered by the same underlying fix - the format: binary path in connectorDataOperationExecutor will be routed through uploadDataAsync rather than being JSON-serialized.

We appreciate you sharing the patched JS files - that level of detail is very helpful for validating the fix. We'll update issue #230 when the release containing the fix is available.