Released on January 20, 2021

Bug fix: An error occurred when the background color of a cell in a Description column was changed in Condensed WBS

The color was changed and saved correctly. Just the error message was displayed inappropriately.

Bug Fix: Handling of network paths may fail in macros calls

In all path where one of the following variables are supported:

•<USER_NAME>

•<PROFILE_PATH>

•<TEMP_PATH>

•<DESKTOP_PATH>

•<MY_DOCUMENTS_PATH>

•<INSTALL_PATH>

•<INTERNAL>

The paths starting by \\ or // (networked) were badly interpreted; some characters were duplicated, possibly resulting in errors.

Bug fix: Error with estimate having ‘ in file name not supported in some functions

Estimate file having ‘ in name caused ‘SQL logic error’ since August 2020 beta versions in Import Settings’s dialog function.

Change: changes rolled back to support older versions of SQL Server

Some recent changes from August 2020 used new MS SQL Server 2016 syntax because Microsoft halted support on older versions. However, some customers still have older versions so we rolled back these changes and Ms SQL Server 2012/2014 are still supported.

However, if you own such old engines, we strongly suggest an update: https://www.wardyit.com/blog/sql-server-end-of-life-considerations/#:~:text=SQL%20Server%202014%20reached%20its,end%20on%209%20July%202024.

Bug Fix: ‘Quantity (Number)’ column fed with ‘1’ when on top of a set in the database of the estimate

When using the QUANTITY_NUMBER column in your logic, you can type ‘0’ in it to ignore the quantity on the considered row (it multiplies the result of the formula by ‘0’).

When you do that on top of sets in the database of the estimate, we have no value to calculate the quantities on child lines. So, at selling-prices calculation time it led to an error message.

Now, we force QUANTITY_NUMBER to 1 on such rows when it contains 0 as we forced the quantity to 1 on these rows when QUANTITY_NUMBER was not implemented.

Bug Fix: Failure in pushing versions could result in nested transaction error

When pushing a version or a progress statement in an estimate normally connected to a management database where this database cannot be accessed could result in a ‘nested transaction’ error.