Export To Exact (binary)

The Export To Exact Binary node stores large data types in Exact (such as attachments, images, or large text fields) by converting them into a binary object.

In Exact Synergy and Exact Globe, entities themselves do not directly support large data types. Instead, this kind of data must be stored separately using the binary service, which allows large content to be uploaded and referenced from within entities.

How it works

To store data such as attachments (files), images, or large text (memo fields), you must first convert this data into a binary object using this node.

Process flow:

1. The content is uploaded to Exact as a binary.
2. Exact stores this binary separately.
3. The system returns a unique ID for the created binary.
4. This ID must then be written to the corresponding field (property) of the target entity in a subsequent step (e.g. via Export To Globe or Export To Synergy).

Configuration

Setting	Description
Content Column	The column containing the data to be converted into a binary. Can contain text, file data, or Base64-encoded content.
Input Type	Defines how the content of the selected column should be interpreted. Available option: AutoDetect, which automatically determines the format of the content.
Chunk Size	Determines how the binary is uploaded to Exact: the content is split into smaller chunks, and each chunk is uploaded separately. Particularly important for large files, to ensure stable and reliable uploads.
MessageId Column	The column name used to store the unique identifier Exact returns after the binary is successfully created. Defaults to MessageId.

File inputs can be reliably auto-detected, but text inputs are ambiguous since they may also contain Base64-encoded data: automatic detection may not always be accurate for text-based inputs.

Output

The MessageId returned by Exact is stored in the configured MessageId Column and can be used in subsequent nodes (such as Export To Globe or Export To Synergy) to reference the uploaded binary.

Tips

• Prefer explicitly setting the Input Type instead of using AutoDetect. This avoids ambiguity and improves reliability, especially when working with text or Base64 content.