Calculation Matrix export via VBT is missing the %vlocity_namespace%__CalculationMatrixRow__c node in the calculationmatrixname_version.json file.

To ensure consistent exports regardless of matrix size, you must switch to a Version-Based Export strategy. This bypasses the API chunking logic entirely.

Step-by-Step Fix:

1. Open your Vlocity Build Tool Job File (.yaml).

2. Add the following parameter to your configuration:

   • separateMatrixVersions: true

When separateMatrixVersions: true is enabled, the VBT uses a custom JavaScript export path. Instead of receiving data in potentially "overwrite-prone" chunks from the API, it executes a single query to retrieve all rows at once for the matrix version. This ensures that the %vlocity_namespace%__CalculationMatrixRow__c node is always present and correctly points to the rows.json file, regardless of how large the matrix is.