7.25.1212 |
  
|
7.25.1212 |
|
Released on May 5, 2026
We have been struggling for months to prepare all files for the migration to .NET 10 (a more efficient, faster, open source framework which will replace .NET Framework 4.8).
The first step for this migration was to bring all assemblies to C# because we still had some major assemblies written in VB .NET. This explains why we didn't provide public beta versions in the last 3 months.
Several betas versions have been created during this period but they had been kept internal (for our own tests).
The conversion has been carried out. The beta C# is now quite stable. So, the future beta versions (7.25120x and 7.26120x) are fully written in C#, ready for the .NET migration that will occur in the coming months (Microsoft will stop support of .NET Framework in 2030)
The current version 7.25.1212 is the latest beta with VB .NET assemblies and reflects the 7.26.0001 official which will be published in the coming days. After this, all upcoming versions will be fully written in C#.
It could happen that minutes Quantity values or values of quantity-related fields were not correctly copied from the source XLSX to the final estimate. For example, if SetDepth field was specified in the source, it could trigger auto-calculation of Quantity and ignoring the Quantity value from XLSX.
When the user activated "WBS sheet in overhead" feature, the WBS sheet was still missing in the overhead after the estimate was reloaded. There was no way to display it. This only happened in some newer estimates, older estimates were OK. The issue was introduced in QDV 7.25.1188.
1.The auto-complete of references or descriptions was not working if there was any remote article or sets database (not a local file) specified in preferential databases, and this DB was not accessible. This could happen, if a remote preferential DB was defined in an estimate (with red heart icon) and then this estimate was opened by another user who didn't have access to this database. Now this situation is handled correctly, and QDV displays the name of the inaccessible DB with red background in the auto-complete drop-down list.
2.The most relevant suggestions for reference or description auto-completion should be those that start with the typed text. If there were many records in the database that contained the typed words in the middle, it could happen that the most relevant results were not listed at all.
3.When using the auto-complete drop-down list, the user can select from which preferential database he wants to get the suggestions. This is done with right or left arrow keys or by clicking on the DB name above the list. The index of this DB is saved in the user settings. When the estimate was then opened after the user removed some preferential databases so that the saved index became too high, an error occurred when he tried to use auto-complete suggestions.
An automatic UI refresh/repaint is triggered after a new column is appended. Values inside the newly added column are now instantly visible without requiring any manual "Check & Repaint" action from the user.
When the user opened the scenario manager, an error could occur when some WBS column headers were merged. For example, if Quantity and Unit had the same first header row. Additionally, an issue causing an extra empty column to appear has been resolved. These changes result in a more accurate and visually consistent display of scenarios.
The “Tabs & Sheets & Columns” tab in the permissions window contains one row for each editable column in each overhead sheet. There was a limit of 999 rows that could be editable. If the overhead workbook contained many sheets with many editable columns, this limit could be exceeded, and remaining rows couldn’t be edited by the user.
When merging estimates (Home/Tasks/Merge) the Quantity_For_Evaluation_WBS is copied with the contents of the minutes if it exists. Except if the flag " Quantity_For_Evaluation_WBS follows WBS Quantity is set".
When the user created a new task or a sub=task, the quantity was set to 1. But the WBS_Formula_For_Quantity was not set, it was empty. After compute all, the empty formula was evaluated and the result 0 was written to quantity and the initial 1 was lost. Now the WBS_Formula_For_Quantity is set to 1 in new tasks, so it matches the quantity.
An overhead sheet may contain various controls, such as checkboxes, listboxes, etc. Moreover, rows and columns in these sheets may be hidden by using special texts {hiderow} and {hidecolumn}. If some controls were placed on rows or columns that should be hidden, then they were “lost” on the next opening of the estimate. But this only happened when a visible area was set for the sheet with View > Show > Visible area option.
The controls will not be lost anymore in the fixed version. They were not lost in fact, they were moved to the closest visible row above and their height was set to zero, so they were invisible. The user can resize and move them back to their original position in Excel.
The values of distribution fields in WBS were lost in all older versions or progress statements. This could be seen if the user has displayed an older version. This is fixed now and the data is persisted for all newly created versions.
When recording a set to a database, each extra (derogation) field now has three checkboxes instead of one: Article, Virtual Article, and All. This lets the user pick whether the field value is copied only on real articles, only on virtual articles, or on both.
When Keep depth is checked and the only virtual article in the set is its header row, the Virtual Article and All columns are disabled: that header row is skipped at recording time anyway, so the user can't accidentally select fields that would end up as empty columns.
If a previous selection in a now disabled column is still visible, it is treated as unchecked during save.
When recording a set with Keep depth checked and answering No to the "create virtual articles" question, the first non virtual row right after the header (for example an article from an external database) was missing in the recorded set. This only happened when the set itself didn't belong to an external database, i.e. when its database path and database source were empty.
In that case the header row had no .qdb or .grp extension, so it was removed during the virtual-article cleanup just like the virtual articles. The indices then shifted, and the Keep depth code that's supposed to skip the header at index 0 ended up skipping the first real article instead. Fixed by leaving the header row in place during the cleanup the Keep depth code already handles the header correctly afterwards.