Difference between revisions of "Auto Aggregate items using hierarchies"
| Line 27: | Line 27: | ||
'''Important''' | '''Important''' | ||
| − | As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates. The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit. | + | As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates. |
| + | |||
| + | ==Parameter detail=forceAggregates== | ||
| + | The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit. | ||
When a data query that would normally produce hierarchy aggregates matches more series than a configured threshold, the system will not compute or return aggregate series by default. Instead it will return the underlying raw leaf series only. Callers that genuinely need the full aggregate response can opt in with detail=forceAggregates. The threshold is configurable via a JVM system property. | When a data query that would normally produce hierarchy aggregates matches more series than a configured threshold, the system will not compute or return aggregate series by default. Instead it will return the underlying raw leaf series only. Callers that genuinely need the full aggregate response can opt in with detail=forceAggregates. The threshold is configurable via a JVM system property. | ||
| + | |||
| + | The default number of series is 10,000 but cand be changed, click here [[System_Properties |to read more.]] | ||
Revision as of 01:59, 24 September 2026
Overview
Auto Aggregation changes the result of a data query as see in Fusion Data Browser or via Webservices.
To use the Hierarchy feature, first you must create a hierarchy using the appropriate codes. Read more about creating a Hierarchy in this article.
Next, link the hierarchy to a dataflow and using the Aggregation area.
Use the Add Hierarchy button to select which Dimension and which Hierarchy is to be used.
To see the effect of the Auto Aggregation:
- Fusion Data Browser will display the individual items along with a Total.
- When querying the data, the Total is available along with all the individual items which make up the total.
Important As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates.
Parameter detail=forceAggregates
The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit.
When a data query that would normally produce hierarchy aggregates matches more series than a configured threshold, the system will not compute or return aggregate series by default. Instead it will return the underlying raw leaf series only. Callers that genuinely need the full aggregate response can opt in with detail=forceAggregates. The threshold is configurable via a JVM system property.
The default number of series is 10,000 but cand be changed, click here to read more.
