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.

Salesforce imposes a heap size limit of 6MB for synchronous transactions and 12MB for asynchronous transactions. This means that the total memory consumed by your Apex code during a single transaction cannot exceed these limits, depending on whether the execution is synchronous or asynchronous.

This can become an issue when the Reporting Engine processes large datasets or exports reporting files that exceed these limits. To prevent heap size errors, an enhancement has been implemented to automatically split the file into multiple parts if the heap size exceeds a predefined threshold (e.g., 80% of the limit). This threshold is configurable in:

Custom Settings → Reporting Export App Settings → Heap Size Threshold (%)

However, managing heap size is complex, as every step - including data processing, file compilation, and variable assignments - contributes to the heap limit. Even with the threshold in place, users may still encounter errors.

For example, if the heap size is currently at 79% and the threshold is set at 80%, the process continues. However, if a subsequent action in the automation processes a large dataset, consuming an additional 30% heap, it will still result in a heap size limit error.

Best Practices to Avoid Errors

To further reduce the risk of heap size errors, users are strongly encouraged to:

• Set Data Generator Job Mode to “Batch”
• Reduce Data Generator Batch Size

These adjustments help optimize memory usage and ensure smooth processing.

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.