Released on November 21, 2024
This happened when the overhead was exported to Excel with QDV in one language, for example EN. Then QDV was started with another language, for example FR. If the user imported the overhead from Excel, an "Operation requires a valid password" error occurred. This could possibly happen also when Edit overhead in Excel, but only under very rare circumstances.
An error occurred in nomenclatures if a minute field of type text with defined "List box data" had a formula. This was possible, for example, with the MUST_PURCHASE field.
An error occurred when importing a child estimate or merging databases of estimates. This happened, if a line in DB of estimate had a reference to an article with an embedded Word, Excel or other file.
A warning was displayed, if the edited FORMULA_FOR_QUANTITY contained a comma as a decimal separator. So, it was impossible to enter decimal numbers on non-English systems, such as French. Similarly, it was impossible to use a semicolon character “;” as a parameter separator in Excel functions. This issue was introduced in the previous QDV 7.24.1158 beta.
An error occurred if the user tried to paste a name into the bottom workbook in Expanded WBS. This only happened if the estimate contained multiple WBS fields from minutes that had the same main breakdown field.
TARIFF_DATE of Tarifeo Article database was missing, now it is imported and updated as expected.
The IScenario.Values thrown an exception if a task was deleted from WBS while it still was defined in scenarios. Moreover, the IScenario.GetValueForTask, IScenario.GetValueForTaskByHexID and IScenario.GetValueForTaskByGuid thrown an exception, if the IScenario.Values property was not accessed before. This issue was introduced in QDV 7.24.1153