Salesforce enforces the following heap size limit. If the Reporting Engine processes large datasets or exports large files, exceeding these limits can cause errors.

• Synchronous Job: 6MB
• Asynchronous Job: 12MB

To prevent this, an enhancement now automatically splits files into multiple parts when heap usage surpasses a configurable threshold (e.g., 80% of the limit). This setting can be adjusted in: Custom Settings → Reporting Export App Settings → Heap Size Threshold (%)

Example:

When the process detects that heap usage is approaching the configured threshold, the file PCO.txt will be automatically split into multiple parts:
📂 PCO_Part_0001.txt
📂 PCO_Part_0002.txt
📂 PCO_Part_0003.txt
...and so on.

📌 Important: Users must manually merge the file parts into a single file if needed.
 

Best Practices to Avoid Errors
The heap size management remains complex. Every operation—data processing, file compilation, and variable assignments—contributes to the limit. Even with the threshold in place, transactions may still hit the heap limit if additional processing occurs unexpectedly. If you continue to experience heap size errors, try the following:

• Reduce Data Generator Batch Size
• Reduce the Heap Size Threshold (%)

These adjustments help optimize memory usage and ensure smooth processing.

The RIO Education Reporting Engine already supports merge fields from the Reporting Export record, such as {!from}. With this enhancement, merge fields are now also supported in Leading/Trailing Values within the Export Data Field.

For example, if a user wants to prefix the student ID with the reporting year (e.g., 2024-1071116664), they can configure the Export File Configs by setting the Field Name to the student ID field. Then, in the Export Data Field, they can define a Leading/Trailing Values  as {!reportyear}-, ensuring the reporting year is automatically prefixed to the student ID.

Users can now round numbers up or down to a specified number of decimal places, as defined in Export Data Field → Rounding Decimal Places.

For example, if Rounding Decimal Places is set to 3, the number 8.7476 will be rounded up to 8.748. This enhancement ensures greater precision and flexibility in data export formatting.

Configuration Steps:

To enable this feature, users need to configure the following fields in the Export Data Field:

• Retain Decimal Points = true
• Number Rounding Mode (Select rounding method)
• Rounding Decimal Places (Specify the desired decimal places)

By setting these fields appropriately, users can ensure consistent and accurate rounding in exported data.