New: Add Gantt Duration Months column for Minutes and Nomenclatures tabs

Added a new column (as a free special field) for the Minutes and Nomenclatures tabs. This converts the duration of a Gantt task (static task, meaning it calculated the calendar duration in months) using the formula Duration / (365/12). The decimal precision is 2. This maintains backward compatibility with previous QDV versions.

If an estimate containing this new column in the Minutes and Nomenclatures tabs, is opened with an older QDV version, the columns will be hidden automatically. When the estimate is reopened on the newer QDV version the columns will unhide back again.
A small fix was also provided for the previously added GDM column in the Expanded WBS tab. SaveFieldToDB now writes a HiddenColumns row for GDM when saving as admin, so the GDM-specific load path finds HiddenByUser=true and the Insert Fields dialog correctly shows GDM as a hidden insertable field.

Fix: The Gantt.WriteItemToGanttDiagram could throw an exception (macros)

Clearing Gantt task relations via API is done by setting the IGanttItemInfo.TaskRelations property value to an empty list. This has caused an exception when the Gantt.WriteItemToGanttDiagram was called after setting the TaskRelations property.

Fix: Error when saving or exporting reports

An error occurred when exporting report to Excel or saving report profile which contained merged cells outside of visible range. For example, a cell in the last visible column was in a merge area which spanned beyond that column, e.g. in Next Page header definition.

New: Add Free- and Total Float(Slack) in the Planner tab Gantt chart

Two new columns were implemented in the Planner tab Gantt chart. These calculate the Free- and Total Float for each Gantt task in the project. Currently the calculation is expressed in calendar days, treating all tasks as static and ignoring non-working day/hours calendars. Backwards compatibility is not affected if an estimate is saved with these 2 new columns.

Fix: Building IDIQ databases

When building an IDIQ database from a WBS, an article coming right after a set was always implemented as VIRTUALARTICLE in the database of set.

Fix: Settings forced selling prices to 0 from databases of sets

The mechanism used to invalidate articles in the framework of IDIQ contracts with database of sets was based only on explicit values in ForcedSellingPricePerUnit and TakeForcedSellingPrices fields. However the database of set could invoke regular databases of sets, not designed for IDIQ contracts. Such databases generally don’t have these two fields because they are also used as regular set databases.

Now, if you call a set from a parent set and explicitly force it’s selling price to 0 (using ForcedSellingPricePerUnit = 0 and TakeForcedSellingPrices =1 in the set), the null value will be automatically propagated to all articles referenced in the set, including articles in possible sub sets.