Last updated:
Export To Data clip
The Export to Data clip node writes data from a dataflow into a Dataclip, for use in dashboards, forms, or for monitoring purposes.
Configuration
Section titled “Configuration”| Setting | Required | Description |
|---|---|---|
| Connection | Yes | Connection to the Any2Info platform where the Dataclip is stored. |
| Collection | Yes | The collection the Dataclip belongs to. |
| Dataclip | Yes | The Dataclip to export data to. A new Dataclip can be created directly from this property. |
| Action | Yes | Defines how the incoming data is written to the Dataclip: see Action types below. |
| Advanced | No | Allows configuration of the mapping between the incoming dataset and the headers of the Dataclip. |
| Wait | No | Determines whether the dataflow should wait until the export is fully processed on the server. If disabled, the flow continues as soon as the data is received by the server. |
Action types
Section titled “Action types”| Action | Behavior |
|---|---|
| Replace | Replaces the entire contents of the Dataclip: all existing records are removed and the incoming data is fully reinserted. |
| Insert | Inserts new records. Records with an existing key are ignored; only new records are added. |
| Update | Updates existing records. Only records with a matching key are updated; records without a match are ignored. |
| Insert or Update | Upsert behavior: if the key exists the record is updated, otherwise it is inserted. |
| Delete | Removes records matching the incoming keys. Only the unique header column needs to be mapped. |
| Except | Removes all records except those present in the incoming dataset: the inverse of Delete. |
Input / Output
Section titled “Input / Output”| Direction | Type | Description |
|---|---|---|
| Input | Dataset / Table | The dataset that will be exported to the Dataclip. |
| Output | Dataset / Table | The same dataset as the input, passed through unchanged. |
When to use it
Section titled “When to use it”Use the Export to Data clip node when data from a dataflow needs to be stored in a Dataclip for use in dashboards, forms, or for monitoring purposes.
Typical use cases include:
- Displaying data on dashboards
- Providing selectable or prefilled data in forms
- Logging or tracing dataflow execution
- Inspecting intermediate or final dataflow results
- Disable Wait when using Dataclips for logging or tracing to prevent unnecessary delays in the dataflow.
- Enable Wait when it is important that the data is fully processed before continuing the flow.
- Use the Advanced mapping to explicitly control how dataset columns map to Dataclip headers.