Navigation:  7.18 > 7.18.0679

Released on October 10, 2019

Bug fix: Sheets get unprotected in overhead

When double clicking on the default currency, unit of the list or default material or workforce kind, and having no rights to adapt this, then the sheet was left unprotected.

Bug fix: Incorrect figures in WBS due to rounding

When a rounding of 10, 100 or bigger is configured for the WBS (proportional or not) then in some cases this could lead to invalid figures In the WBS. This happened only when new 'Spread fixed costs on selling prices' features is activated.

Bug fix: Update rows for cost/price + currency fields

The normal behavior is that the material cost and all forced prices are always updated together with their currencies. However, when one of those is not allowed (because it has a formula or because it is not allowed via the field manager or permissions), then still the other part is proposed for updating.
In this case however, still both parts were updated. This is changed now so that only the indicated part is updated.

Above problem had also a weird effect when the field had a replacement field. Because the original field was always read, and afterwards replaced, it was not possible to exclude the replacement field from updating.  In order to exclude it, also the corresponding currency field needed exclusion.

Change: Handling of replacement fields.

Let’s say we have an original field A and its replacement field Replacement_A.

Case 1: Database contains A and Replacement_A
In direction database to estimate we read both fields, but field A is ignored. Replacement_A from database writes Replacement_A in estimate. (Until now, field A from database was written as Replacement_A in estimate).

In direction estimate to database, Replacement_A from estimate is written as A and as Replacement_A in the database. (Until now Replacement_A was written only as A in the database)

Case 2: Database contains only A (which is the normal replacement scenario)
In direction database to estimate, field A from database writes Replacement_A in estimate. (Nothing changed)

In direction estimate to database, Replacement_A from estimate is written as A in the database. (Nothing changed)

Case 3: Database contains only Replacement_A
In direction database to estimate, field Replacement_A from database writes Replacement_A in estimate. (Until now this did not work for update rows, because original field A was expected in the database)

In direction estimate to database, Replacement_A from estimate is written as Replacement_A in the database. (Until now this was written nowhere because it was tried to write to non-existent field A)