Hello!
I have the following collection structure:
- Transportation
1.1 Cargo Locations
The Cargo Locations collection has a Price field. The Transportation collection has the fields “% growth price location” (type - percentage) and “Calculation” (type - Boolean).
When adding a new Transportation record, a sub-table is placed for adding records to the Cargo Locations collection. At the same time, field rules are configured that allow the initially entered value in the Price field of the Cargo Locations sub-table to be increased “on the fly” by a specified percentage (the “% growth price location” field of the Transportation collection). This is done according to the rule - when you click on the “Calculation” checkbox field (the last value in the Price field is multiplied each time you click on the checkbox so that the value takes on the “true” parameter).
Everything is done correctly, the calculation is performed, and the result is correct (for example, if I enter 1000 in the Price field and 100% in the “% growth price location” field, and then click on the “Calculation” checkbox, the value becomes 2000, i.e., 1000+100%. If I repeat the iteration, the value will be 4000, and so on).
But I added another condition, whereby the nested sub-table (which, according to the original database connection structure, is a “many-to-one” field) acquires the “easy reading” property when the “Calculation” checkbox is clicked — that is, in this way I disable/hiding the possibility of adding a new record to the Cargo Locations subtable.
At this point, the calculation of the primary value is doubled, not according to the calculated “formula.” That is, if I enter 1000, the result of the iteration becomes 4000 instead of 2000.
I don’t understand why this happens.
For clarity and better understanding, see the video file below.
You can reproduce the problem on the page
https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/on02hifb4i3/popups/49sblmzszn2/filterbytk/346796233850880/tab/du7brynzz1c
To ensure that the iteration is performed correctly, you need to disable the reference field rule (screenshot below), which disables the ability to add a row to the subtable…
