Navigation:  7.19 > 7.19.0769

Released on June 5, 2020

This version is the beta image of the official 7.20.1

New: More flexibility in target value function

When using the Target Value function, you must select a line in the minute which support the difference to reach the target. This line is automatically forced at calculation time.

However, in order to keep credible figures, when the compensation amounts for more than 50% of the selling price of the row, you get a warning message.

Now, if you set the selling price of the line to 0 (using a blank line), you explicitly tell QDV that you allow any compensation on that row. So when you just deliver WBS figures to your customer, there is no reason to block this because the compensation row will never be show.

Of course, as soon as the row has a selling price, when the adjustment account for more than 50%, the message still appears.

Bug Fix: Styles loaded a first usage of QDV Tools for XL

Some users experimented gray cells in the mapping sheets when using QDV Tools for XL for the first time. It's now fixed.

Change: Formulas comments no longer displayed when rows are coming from the base

When rows belonging to as set coming from the base, these row do not exist in the minutes, they are just reflected from the database of the estimate.

But if you enable the flag Edition of the base from the minute, you can still input values in the Quantity column (when you don't use the Formula_For_Quantity column).

However, entering a formula from there can be confusing because the formula in the Quantity column is valid only in the focused set. It makes certainly no sense for other instances of the same set because they can have other parent quantities.

We adapted that to hide the meaningless part of the comments.

So now, when you input such a formula in the Quantity column (or in the column which is a replacement for the Quantity column) the formula part of the comment is no longer displayed in these light blue lines.

Of course, the rest of the comment is still visible because it can be useful.

When you go to the corresponding row, in the database of the estimate, you still see the whole comment because there, it has a meaning:

Comments behave as before for all other columns, including Quantity_Per_Unit. Quantity_Per_Unit has same meaning in all instances..