To work around this issue, you can apply FILTER function (when possible) for taking from application data to reduce the scope of further grouping and aggregations.
The changes in the hotfix contain the code modification that makes possible to configure GER data sources of the GROUPBY type in the way allowing GER to execute them in SQL, not in memory.
When you design your GROUPBY data source in GER designer selecting target data source, defining grouping and aggregation parameters, GER informs you whether the configuring GROUPBY data source will be performed in SQL. Pay attention to the following:
- GROUPBY data source will be performed in SQL only when for grouping you selected the data source that refers to one of the following GER data sources:
o Data source of the ‘Table records’ type;
o Data source represented as an expression using the function FILTER.
Note that a GROUPBY data source will not be performed in SQL when you configured in it more than one aggregation for same field of the underlying table of the grouping data source. To avoid this limitation, configure individual GROUPBY data sources for each aggregation (if applicable).