Summary Validation
A Summary is where → group → having → order → page. Its rules guarantee that every Order and Having field can actually be resolved against the grouped projection.
Rules
| Rule | Error Code |
|---|---|
GroupBy is required (not null) | ArgumentNullException |
| Order fields must exist in GroupBy fields or aggregate aliases | SummaryOrderFieldMustExistInGroupByOrAggregate({field}) |
| Having condition fields must reference aggregate aliases | HavingFieldMustExistInAggregateByAlias({field}) |
Note
After grouping, the only addressable members are the GroupBy keys and the aggregation aliases — that is what Order and Having can reference.
Related
- Summary class
- GroupBy rules — the nested
GroupByis also validated. - Summary JSON example