Batch run

Run the same SpreadsheetWeb API request repeatedly and compare how different versions of the underlying workbook affect the results. This lesson combines batch calculation testing with transaction-based version control, two useful tools for validating model changes before updating an integration.

Run a batch calculation

Begin with a calculation request that already contains the required inputs and outputs. Randomized input formulas are especially useful because each iteration can exercise a different scenario.

1. Copy the calculation request from API Toolkit.
2. Open Batch Calculation and paste the request.
3. Set the iteration count. The interface supports up to the limit configured on the SpreadsheetWeb server.
4. Select Batch Run.
5. Open individual results to review the input values and outputs produced by each request.

Batch runs make it easier to test many combinations without manually submitting each calculation. In the lesson, ten requests are executed and the randomized age produces a different premium for each iteration.

Publish an updated workbook transaction

Spreadsheet models normally change over time as formulas, rates, lookup tables, or business rules are revised. SpreadsheetWeb preserves these revisions as application transactions.

To create another published transaction:

1. Update and save the Excel workbook.
2. Open the application in Design.
3. Start or edit the current transaction and upload the revised workbook.
4. Publish the transaction.

The original and revised workbook versions can now be tested separately from API Toolkit.

Select a version by transaction sequence ID

Choose a published transaction in API Toolkit and run the same request against each version. API Toolkit places the selected version in the request's transaction sequence ID, allowing an integration to target a specific workbook revision explicitly.

This is useful when validating a new model against a known baseline or when an external process must continue using a particular published revision.

Select a version by transaction date

You can also request the transaction that was active at a particular date and time. API Toolkit adds the transaction date selection to the request, and SpreadsheetWeb evaluates the calculation using the workbook version published at that moment.

Date-based selection is useful for reproducing historical results when the exact sequence ID was not stored. Whether you use an ID or a date, keep the version selector with the request so the calculation can be reproduced later.