You can use RemoteTurnkeySetByteArray only when maintaining an existing legacy integration that writes a byte array to a Turnkey site; for new integrations, use the normal REST API to post or put data.
Status
RemoteTurnkeySetByteArray is deprecated. Do not use it in new development.
This operator belongs to a lightweight, legacy protocol that lets one Turnkey site communicate with another Turnkey site. The protocol identifies the target by its ViewModel name, root object, and column name, then writes a new value to that column.
A byte array is binary data, for example the contents of a file or document. In a legacy call, this operator sets that binary value in the target ViewModel.
Use REST for new integrations
Use the normal REST API when you need to create or update data between applications or sites.
For example, if an external system must upload document content to an application, implement the operation as a REST POST or PUT rather than calling RemoteTurnkeySetByteArray. This keeps the integration on the supported API path instead of relying on the deprecated RemoteTurnkey protocol.
Maintaining an existing legacy integration
If your solution already uses RemoteTurnkeySetByteArray, treat it as a maintenance-only dependency.
- Identify the target ViewModel, root object, and byte-array column used by the existing call.
- Verify that the receiving Turnkey site still exposes the expected ViewModel and column.
- Preserve the existing behavior while you plan a REST-based replacement.
- Move new write operations to REST rather than extending use of this operator.
The legacy protocol uses the ViewModel name, root object, and column name as its target information. Changes to any of these target elements can prevent the remote write from reaching the intended byte-array column.
Related legacy RemoteTurnkey operations
RemoteTurnkeySetByteArray is part of the same legacy protocol as operations for reading values, running actions, and closing a remote session. Review the related operators when maintaining an existing integration, but do not use them as a basis for new integrations.