7.21.0011 - OFFICIAL http://www.iaes-software.com/downloads/Setup_QDV_7_21_11.exe |
Released on June 6, 2021
The Unit field was not properly displayed in top rows of each task in the minutes view after import of an estimate made with partner applications (SPIGAO, VECTEUR+, BIMMETRE, etc.)
The following fields: QUANTITY_NUMBER, QUANTITY_FACTOR, QUANTITY_PERCENTAGE were lost when a set was manually disconnected from the database of the estimate.
it was possible to insert QuantityInMinutes and QuantityInOptions in a report of type minutes. This must be reserved to nomenclatures.
When one drops a set or an article from an external database to the database of the estimate or pushes such data to the database of the estimate by using the centralized storage option, the main lines of sets (headers) or orphan articles get now value 1 in their Formula_for_quantity field (meaning that formula stored in the physical database is ignored in these lines).
This is convenient because a specific formula has no meaning on such rows in the database of the estimate. If you attempt to store variables in such databases (like [QEval]) they cannot be interpreted in the database of the estimate.
We enforced the following: If you use a replacement column for the quantity column in the minutes, this replacement column must have a null default value as soon as the FORMULA_FOR_QUANTITY column is implemented.
We saw some estimates having a different default value but this is not compatible with sets and the FORMULA_FOR_QUANTITY column.
Anyway, whatever the columns in your layout, it’s not recommended to use such a different default value in the replacement column of the quantity because all rows having a quantity are computed. It’s better to use conditional formatting if you want to tell the user that there is a missing quantity.
In the conform Gantt diagram (external function), when conforming the diagram to the WBS, creating sub-tasks from a grand-child didn’t work well. An error message appeared. Macro has now version 5.26.
When deleting users (in the sharing window) from a child which has grandchildren, the deletion caused the deletion of the child’s name too. For this reason, tasks previously allocated to the child were no longer accessible.