Memory Threshold Issue in Production Dashboard with Large data

You will have to reduce the volume of data queried. You might have to rebuild the record based Bar Chart by querying the data yourself and manually feed it into a bar chart.

You can reduce the use of a!forEach() and nested loops when processing large datasets. Instead, try to use built-in Appian functions to manipulate large datasets more efficiently. I faced the same issue, and it was resolved after reducing the use of a!forEach() loops.

Few suggestions you can try one by one and see which one suits best to improve performance:

1. Check and apply indexes on database tables on fields that are used for filters, querying etc in the bar chart field.
2. Limit data query so that only what is needed is queried. E.g. selection columns to get only relevant data columns, paging query with 0 batch size and fetchTotalCount as true if only data count is needed and not data rows etc

   a!queryRecordType(
     recordType: 'recordType!HS',
     pagingInfo: a!pagingInfo(1, 0),
     fetchTotalCount: true()
   )

    

3. As dataset is large consider creating a store procedure to filter and aggregate data based on date filters and return data to render bar chart instead of filtering and aggregating in Appian expression.
   
    

Aggregate in the DB using a!queryRecordType() with aggregation and grouping, don't pull raw rows into the ER or chart. For 1-year date ranges, don't query live transactional data, instead create a new summary record type backed by a scheduled rollup process and query that.

Hi ,

we noticed that the error occurs even when querying data for just a 1-month date range. We are retrieving only two fields (an ID and a Boolean field), yet we still encounter the "Memory threshold reached during output conversion" error. There are no forEach loops, no iterations, and no complex logic in the Expression Rule. The rule simply executes a queryEntity(). We are not sure what could be causing the memory issue in this scenario.