IEstimate.RunQdvRequest (String, String, Boolean, Boolean, ref MacroExecutionError, Boolean) Method

Executes a QDV request. If any anomalies are added by the request, a window with the list will be optionally displayed when the request has finished.
Sub RunQdvRequest( _ 
ByVal requestName As String, _ 
ByVal wbsScope As String, _ 
ByVal includeDbOfEstimate As Boolean, _ 
ByVal includeOverheadMinute As Boolean, _ 
ByRef executionError As MacroExecutionError, _ 
ByVal showAnomalies As Boolean
)
This language is not supported or no code example is available.
void RunQdvRequest( 
string requestName
string wbsScope
bool includeDbOfEstimate
bool includeOverheadMinute
ref MacroExecutionError executionError
bool showAnomalies 
)
This language is not supported or no code example is available.

Parameters

requestName
string

The request name (not a request ID).

wbsScope
string

The task hexID significant part. An empty string means no task in WBS. For example, '001' means entire WBS.

includeDbOfEstimate
bool

Indicates whether to include also database of estimate into request execution scope.

includeOverheadMinute
bool

Indicates whether to include also overhead minute into request execution scope.

executionError
MacroExecutionError

Returns the errors produced by the request execution.

showAnomalies
bool

Indicates whether a window with the anomalies list will be automatically displayed, if any anomalies were added by the request with an "Append_Anomaly_List" verb. The list is shown after the request has finished.

Remarks
 
Execution of requests affects the Anomalies property. When a request is started, the anomalies are automatically cleared. When a request has finished, the anomaly list is checked whether it contains any anomalies added with an "Append_Anomaly_List" verb. If the list is not empty and the showAnomalies is set to true, a window with the list will be automatically displayed. And the Anomalies property will be correctly set. So the anomalies can be accessed programmatically through the Anomalies property.

The execution stops on the first error. This error is then returned in the executionError argument. Since the MacroExecutionError is a structure, you cannot test it for null reference (Nothing in Visual Basic), when the method finishes. Instead, test its MacroExecutionError.ErrorMessage property. When you call the method, set the MacroExecutionError.ErrorMessage property to null reference (Nothing in Visual Basic) and when the method finishes, test whether the value is null reference (Nothing in Visual Basic) or an empty string.

Version
 
Available since QDV 7.19.754.

.NET Framework

Supported in: 4.8, 4.7, 4.6, 4.5.2

In this article

Definition