Navigation:  7.24 (QDV 2024) > 7.24.1164

Released on December 22, 2024

New: Extension of Tarifeo Article databases

Tarifeo\Update whole database - warning when database contains more than 100 articles. Waiting bar while updating articles.

Estimate - Data\Update rows function - Tarifeo articles are updated like when we drop an article to an estimate from a Tarifeo database.

Fix: Child estimate file was not created in some cases

No child file was created in full transparency mode, if the "Export entire content of the database of estimate" option was not selected. No warning was displayed. The issue was introduced in QDV 7.24.1158 beta.

Fix: Cleanup database of the estimate didn’t work

The "Cleanup database of the estimate" operation failed with an error. The issue was introduced in QDV 7.24.1158 beta.

New: Edit Scenarios – Prevent to save changes in scenarios manager dialog while a scenario name is empty

There is new warning in case scenario name is missing - scenario name is empty and (parent name is not empty or there is at least one quantity in the column).

Fix: Excel tab name limitation is reached when creating Excel blank report for estimate with timeframe

Long TF field name like TF_TIMEFRAME123456_InputPerUnitPeriods couldn't be created as {TF_TIMEFRAME123456_InputPerUnitPeriods} due to Excel sheet name limit so it is now created as {TF_TIMEFRAME123456_InputPerUn}.

New: Ability to import “FORMULA_FOR_QUANTITY” from a child estimate in non-transparency mode

It is now possible to preserve the FORMULA_FOR_QUANTITY values when a child estimate is imported to the parent in non-transparency mode. This is only done if the user selects to “provide the parent with all detailed lines” option. And because the FORMULA_FOR_QUANTITY may contain references to WBS variables and to global variables that start with a dot, these variables are imported as well.

If there’s a conflict between the global variables with a dot in the parent and in the child estimate, the user is informed, and he can select one of the actions to be performed:

 

1.Use from the parent,

2.Use from the child. When importing a variable from the child estimate, the original variable in the parent will not be changed. Instead, the imported variable will be renamed. The new name will have a suffix with the child owner name, for example, "VAR1_User1". The imported formulas will be adjusted accordingly. If the new name already exists in the parent, it means the variable was imported before. In such a case, the variable in the parent will be overwritten with the variable from the child.

3.Cancel the import.

 

All this new functionality is reflected in the API (macros) as well. There’s a new GlobalVarsConflictResolution property in the Qdv.CommonApi.Sharing.ChildEstimateImportOptions class which allows for detailed conflict resolution. Several helper classes and enums were added to make it work.

Fix: Spreading amounts to WBS didn’t work well when spreading branches

If, in the WBS distribution feature you attempted to direct the amount of a chapter to several tasks, the first task only was fed. Other tasks were ignored and no error message were posted.

New: The ISet.GetInputFields() method in the API (macros)

The new ISet.GetInputFields() method was added to the API. It will get all the input fields for a set from the sets database. This list may be directly passed to the IMinute.InsertSetAtRow method which makes it much easier to be used.