Result
caution
Available only in Pipelines of External Objects (entities) operations.
Result is a Pipe for finalizing the result of a synchronous External Object operation Pipeline. The result is returned to the platform interface and displayed to the user.
Features
- An empty result is not an error.
- Result does not have to be the last Pipe in the chain — after finalizing the result, you can execute additional logic (for example, close a session).
- A Pipeline can contain multiple Result pipes, but none of them should be a child of another Result (the result is finalized only once per branch).
- The result must be an object or an array of objects.
Parameters
| Field | Type | Required | Description |
|---|---|---|---|
path | string | No | Path to the field from which the result is taken. Supports templating. If not specified — the result is taken from $in.data |
caution
To return an array or an object, use the $# prefix. The $ prefix will return the value as a string, which will cause an error.
Possible Errors
params.pathis specified, but the format is incorrect or the field is not foundparams.pathis not specified, and thedatakey is missing in$in
Examples
Correct Example
$#in.data.categories contains an array of objects:
{
"id": 10,
"type": "result",
"params": {
"path": "$#in.data.categories"
}
}
Result from an SQL Query
When used with the SQL pipe, the query result is available in $in.sql_query. Use the $# prefix to preserve the original type (object or array):
{
"id": 300,
"type": "result",
"params": {
"path": "$#in.sql_query"
}
}
This pattern is used in all External Objects operations with SQL: Read, List, Create, Update, Delete.