Skip to content
Cyoda Documentation
Settings

INVALID_AGGREGATION_FIELD — aggregation field is not a scalar JSONPath

cyoda-go version 0.8.4

errors.INVALID_AGGREGATION_FIELD

Section titled “errors.INVALID_AGGREGATION_FIELD”

NAME

Section titled “NAME”

INVALID_AGGREGATION_FIELD — an aggregation’s field is not a JSONPath that denotes a single scalar.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Raised by POST /api/entity/stats/{entityName}/{modelVersion}/query. An aggregation field obeys exactly the grammar a groupBy path does — a required $. leader followed by dot-separated segments of ASCII letters, digits, _ and -, with no bracket-quoted access, array subscript or projection, recursive descent, whitespace or non-ASCII character. See cyoda help errors INVALID_GROUP_BY_PATH for the grammar and the rejected spellings; the message names the offending field and the reason.

The reserved token state is groupBy-only. There is no defined aggregate over lifecycle state, so state as an aggregation field is just an identifier missing its $. leader and is rejected here.

A well-formed path whose value is absent or non-numeric at runtime is not an error: those entities are skipped for that aggregation, and a bucket with no numeric samples reports null.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • crud
  • errors.INVALID_GROUP_BY_PATH
  • errors.INVALID_AGGREGATION_OP

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help crud — Entities are instances of models. Each entity has a UUID, a model reference (entityName, modelVersion), and a lifecycle state managed by the workflow engine. Creating an entity requires the referenced model to be in LOCKED state. All write operations run within a Cyoda transaction and return a transactionId alongside the affected entity IDs.
  • cyoda help errors INVALID_GROUP_BY_PATH — Raised by POST /api/entity/stats/{entityName}/{modelVersion}/query. Every groupBy entry other than state must match the wire JSONPath grammar — a required $. leader followed by dot-separated segments of ASCII letters, digits, _ and -:
  • cyoda help errors INVALID_AGGREGATION_OP — Raised by POST /api/entity/stats/{entityName}/{modelVersion}/query. The supported operators are sum, avg, min, max and stdev, spelled lowercase. Anything else — including count, an uppercase spelling, or a typo — is rejected, and the message echoes the value that was sent.

Raw formats

Section titled “Raw formats”