7.25.1181

Navigation:  7.25 (QDV 2025) >

7.25.1181

Previous pageReturn to chapter overviewNext page

Released on May 12, 2025

New: IGlobalErrors.SetGlobalError method in the API (macros)

A new IGlobalErrors.SetGlobalError method was added. For example, it allows clearing the global error message produced by some methods. This is an old way to report errors and is used by some API for compatibility reasons. If the IGlobalErrors.GlobalErrorMessage is not empty, it is automatically displayed by QDV after the macro has finished. However, this is unwanted and annoying in most cases, as you probably detect and handle the errors yourself in your macros.

So, if you want to suppress this message, you can clear the GlobalErrorMessage property by calling the new SetGlobalError at the end of your macro:

context.QdvManager.Environment.GlobalErrors.SetGlobalError("", 0)

New: IGanttTasksAssignation.AddTask method in the API (macros)

A new IGanttTasksAssignation.AddTask method has been added which allows the user to create new instances of IGanttTaskAssignationImage in the user API.

Fix: IMinute.SetFieldValue for "TaskInGantt" didn’t work in the API (macros)

An error was fixed in the API when calling IMinute.SetFieldValue for "TaskInGantt". The value of type IGanttTasksAssignation was not accepted.

Fix: Editing values in nomenclatures could affect incorrect rows in minutes

This could happen if an article from the database of the estimate was a part of a set in the database of the estimate. And in the Minutes, the set was referenced on some line. If the user has edited, for example, QUANTITY_FACTOR field of this article in Nomenclatures, the value was incorrectly applied to the line with the parent set in Minutes.

Fix: IGantt.RemoveGanttItem didn’t work in the API (macros)

Fixed the IGantt.RemoveGanttItem(string uniqueIdentifier) method. This method overload should display a window asking the user if he really wants to delete the Gantt item. Instead, nothing was displayed and nothing was deleted. The other method overload with showConfirmationMessage parameter, if called with False, worked correctly.