Scope: managed applications, ordinary applications.
1. If the system writes records of the accounting register in the multi-user mode in real time, we recommended that you enable the totals separation mode for this register. When the totals separation mode is enabled, users can simultaneously update the balance table even if they have the same period, account, and dimension values.
Otherwise, the balance table of the accounting register might become a bottleneck upon concurrent actions of a large number of users.
See also: Locking reading of balance at the beginning of transactions
Example 1
In the application, the Self-financing register is defined with the Company and Currency dimensions.
Register totals separation is prohibited:
Let's suppose that two users simultaneously post documents that add a record to this register.
Users will lock each other if register records:
- Relate to the same period.
- Relate to the same account.
- Have the same dimension values, that is, a company and a currency.
In practice, it is very likely that the listed conditions are met simultaneously since most users will work in the same period, with one account, and with the same dimension values (Company and Currency). This can lead to waiting upon lock and decrease overall system performance.
To solve this issue, enable the totals separation mode (see the following example).
Example 2
If you allow and enable the totals separation mode for the same register, the situation will change.
Let's allow the totals separation mode (in Designer mode):
Let's enable the totals separation mode (in 1C:Enterprise mode):
After that, competing users will be able to simultaneously write register records even when the period, account number, and all dimension values are identical.
However, if balance is controlled for this register, there will be no effect of enabling the separation mode.