This article provides recommendations for optimizing forms that comply with legislation requirements, and other similar entities (such as reports or spreadsheet documents).

1. Optimize templates by avoiding a large number of columns or merged cells.

You can win a fraction of a second every time a user finishes editing a cell by simplifying a template. We recommend that you use custom column width in each row instead of cell merging (the users will not notice any difference).

2. Calculate the changes on the client-side. Only calculate cells that actually depend on the changed cell.

If your application makes a server call in order to update the form state when a user changes a cell value, this can impact the performance.

3. Do not update button states dynamically based on the currently selected spreadsheet document area.

Instead, make the action tied to a button available only in a specific document area. If you cannot explicitly specify the area, you can implement a user notification explaining why the action is not available.

4. If a server call is necessary, implement a single call.

This example includes two server calls, which is incorrect:

CalculateOnServer("GoodsPage");
CalculateOnServer("TaxesPage");

To correct this, you have to replace the two lines with a single server procedure call, which includes all of the server method calls.