Flow Studio
DataOcean Query Node
Querying the BizFirstGO Data Ocean — the DataOceanQueryNode config, dataset selection, filter and projection DSL, and result shape.
Node Configuration
{
"nodeType": "DataOceanQuery",
"name": "fetchPayrollSummary",
"config": {
"dataset": "payroll-runs",
"filter": {
"employeeId": "$output.fetchEmployee.entityId",
"periodYear": "$json.year",
"periodMonth": { "gte": 1, "lte": 12 }
},
"fields": ["periodYear", "periodMonth", "grossPay", "netPay", "deductions"],
"orderBy": "periodMonth",
"orderDirection": "desc",
"limit": 12
}
}
Configuration Fields
| Field | Type | Description |
|---|---|---|
dataset | string | Data Ocean dataset ID. Available datasets are tenant-specific. |
filter | object | Filter criteria using the same operator syntax as EntityQueryNode (gte, in, contains, etc.). |
fields | string[] | Fields to include in results (projection). If omitted, all fields are returned. |
orderBy | string | Field name to sort by. |
orderDirection | asc | desc | Sort direction. Default: asc. |
limit | int | Maximum rows. Default: 100. Max: 10,000 (Data Ocean supports large result sets). |
Node Output
{
"rows": [
{ "periodYear": 2026, "periodMonth": 5, "grossPay": 5200.00, "netPay": 3900.00, "deductions": 1300.00 },
{ "periodYear": 2026, "periodMonth": 4, "grossPay": 5200.00, "netPay": 3920.00, "deductions": 1280.00 }
],
"rowCount": 2,
"dataset": "payroll-runs"
}
DataOcean vs SQL Query
| Aspect | SqlQueryNode | DataOceanQueryNode |
|---|---|---|
| Source | External database via registered connection | Data Ocean — BizFirstGO's internal analytics store |
| Query style | Raw SQL with @params | Structured filter DSL (no SQL) |
| Row limit | 500 | 10,000 (optimized for analytics) |
| Latency | Low (OLTP) | Higher (OLAP / data warehouse) |
| Credential | Via datasource registration | Implicit — uses execution's tenant access |
Analytics workflows: Use
DataOceanQueryNode for reporting and analytics workflows that need to process large aggregated datasets. Use EntityQueryNode or SqlQueryNode for operational workflows that need current transactional data.