filter-node
The filter-node processing node validates upstream data from a parent named filter-payload: type must match allowedType, with optional JSON or CSV analysis and schemaValidator checks.
When to use it
Use after filter-payload when the graph needs stronger validation (valid JSON files, CSV structure, schema match) before dashboard or analytics nodes.
Limitations
- Expects the upstream parent node instance to be named
filter-payloadin the session template (runtime input map key). - One allowed type per node (
allowedTypestring, not an array). - Warnings on invalid JSON rows do not always fail the node; review processor logs for your deployment.
Configuration
| Property | Required | Description |
|---|---|---|
dataSourceName | yes | Data source identifier |
allowedType | yes | Expected type string (for example json, text) |
schemaValidator | no | Schema object for JSON or CSV validation when set |
The manifest may list schema as required. The processor reads schemaValidator.
Related
- filter-payload
- dashboard-tools runner (container image
dashboard-utils)
Opens your browser's print dialog. Choose "Save as PDF" as the destination.