Released on May 24, 2021
In the database of the estimate, named elements must have a quantity. So far QDV, changed the quantity of such elements to 1 when it was null.
But some users define sometimes these elements inside their sets in the database. So, changing automatically such a quantity inside a set from 0 to 1 for a child element may change the cost of the parent set.
Of course, the best solution is to avoid null quantities (an element having a null quantity in the database can be removed because it’s useless) or to define child elements outside the sets and consume them in the sets.
Anyway, we decided not to restrict this because it’s quite fast and convenient.
To avoid these errors, we now post a message at computing time (compute selling prices) when a named element is found inside a set of the database of the estimate with a null quantity. We no longer fix the quantities automatically. They must be manually fixed.