Dependencies:Missing Dependency Names
- Updated2025-07-30
- 2 minute(s) read
Returns the array of qualified names listing every missing dependency of the given object.
For a standard subVI node, this might be one qualified name for the subVI. For a polymorphic VI subVI node, this might be two names: one name for the polymorphic VI and one name for the instance VI. For typedef controls, only a single name will be returned even if the typedef has nested typedefs that are also missing. Call this property on the nested controls to get the missing nested typedef names.
Special behavior exists for some objects
- Network shared variables: The path is always empty. The object is always considered found even if the library that defines the variable is missing, because the variable may be found at run time.
- Dynamic dispatch subVIs: The path is to the class and name is to the member VI.
- LabVIEW class property nodes: The path is to the class and name is to the member VI even if the member VI is static dispatch. These objects are classified as found if the class is found even if the member VIs are missing.
Remarks
The following table lists the characteristics of this property.
| Short Name | MissingNames |
| Data type | ![]() |
| Permissions | Read Only |
| Available in Run-Time Engine | No |
| Available in Real-Time Operating System | No |
| Settable when the VI is running | No |
| Loads the front panel into memory | No |
| Need to authenticate before use | No |
| Loads the block diagram into memory | No |
| Remote access allowed | Yes |
