Released on October 4, 2024

Improvement: Performance of setting WBS fields values

Greatly improved performance of setting WBS fields. For native WBS fields, it's about 9-12x faster now. For non-native WBS fields, it’s about 2x faster in some cases. The change is noticeable mainly if the WBS values are modified from requests, events or the API (macros).

It affects writing to WBS fields, for example, Set_Value_To_WBS_Column and Copy_WBS_Column_Values verbs in events. The same applies to corresponding IWbs.CopyWholeColumnValues, IWbs.SetValueToWholeColumn and ITask.SetFieldValue methods for macros.

Improvement: More options in the Copy_WBS_Column_Values verb in events

There's a new option to copy the values to branches at the automatically detected position - whether to the bottom or, if not possible, to the top. Previously, this option was missing in the last parameter of the Copy_WBS_Column_Values verb:

Copy_WBS_Column_Values(<Source Column ID>, <Target Column ID>, <0=Do not copy to branches, 1=Copy to branches at top, 2=Copy to branches at bottom>)

The new option has value 3:

Copy_WBS_Column_Values(<Source Column ID>, <Target Column ID>, <0=Do not copy to branches, 1=Copy to branches at top, 2=Copy to branches at bottom, 3=Copy to branches at bottom or top automatically>)

This allows the Copy_WBS_Column_Values verb to work the same way as the Set_Value_To_WBS_Column verb does, which uses the auto-position.

Bug fix: Improved data validation when importing XLSX into Gantt

1.It was possible to import invalid [ and \ characters in the task or group text.

2.The row outline was checked too late. If there was an error, the import was stopped, but the original Gantt was not restored.

3.It was possible to import an invalid owner.

Bug fix: Special fields in the minutes fields manager were not highlighted with green background

This issue was introduced in QDV 7.25.1156.

Bug fix: Incorrect values of some fields for articles in a set in Nomenclatures

The values of the fields that had "Ignored from database of the estimate" set to YES were incorrect on some places in Nomenclatures. It occurred for articles belonging to a set from DB of estimate, if that set was referenced in minutes. An example of such fields is QUANTITY_FACTOR or FORMULA_FOR_QUANTITY.

Bug fix: Wrong cost per unit on chapter with option sub-tasks

If the user modified the total row of a chapter in WBS, and if that chapter contained an Option task, the Cost per unit value on this total row was wrong. Compute all was required to fix it.