Fixing the record size limit error in Dynamics 365 Finance & Operations: A quick guide

Understanding the root cause of this form error?

The primary cause of this error lies in the global buffer size setting for forms within Dynamics 365 Finance and Operations. This buffer acts as a memory allocation that temporarily holds data when joining records. By default, the buffer space is capped at 196608 bytes (about 196.08 KB), which is generally sufficient for most standard operations. However, if your data volume exceeds this limit, the system will prevent form loading to avoid performance degradation. In this case, the required buffer size for the selected data was 224230 bytes, exceeding the system’s default configuration. Therefore, an adjustment is necessary to increase the buffer size to match the needs of your data retrieval, allowing forms to load without issue. Let’s explain this through screenshots: The defined buffer size for default is 196608 bytes and its equal to 196.08 Kilobyte.

The required buffer size for selected data is 224230 bytes.

The fix: Adjusting the buffer size for optimal performance

To overcome this limitation, you can increase the buffer size within the system configuration. However, this change should initially be tested in a development environment to ensure it resolves the issue without causing other side effects. Follow these steps:

Step 1: Access the development environment

Start by implementing the fix in your Dev VM (development virtual machine) environment. Testing changes here allows you to confirm functionality and assess any impact on system performance.

Step 2: Run the buffer size adjustment script

The script below modifies the SYSGLOBALCONFIGURATION table, setting the buffer to a higher value. The script adjusts the VOLATILE_SQLTRANSFERBUFFERKBYTES setting, which controls the transfer buffer for SQL operations.

UPDATE SYSGLOBALCONFIGURATION SET VALUE = 220 WHERE NAME = 'VOLATILE_SQLTRANSFERBUFFERKBYTES';

In this example, the buffer size is set to 220 KB, which should accommodate the record size required (224230 bytes). You can adjust this value further based on your specific data needs.

Step 3: Test and verify

After executing the script, attempt to load the problematic form to verify if the increased buffer resolves the issue. If the form loads correctly without errors, you can proceed to apply this solution to higher environments like UAT (User Acceptance Testing) and, eventually, production.