From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Scripting - Find path of missing VI on block diagram bug?

I have a block diagram with missing VIs that I would like to find the missing path of. The propery "MissingPath" works for standard sub VIs and static dispatch VIs but fails on dynamic dispatch VIs even though the path is shown in the Context Help when I hover over it. Instead it returns Error 42 - Generic error.

 

Is this a bug?

 

Test VITest VI

 

ResultsResults

Example project attached. Missing VIs are intentional - just click ignore all and run Missing path test.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
Download All
0 Kudos
Message 1 of 5
(2,229 Views)

I'd say it's a bug. Haven't found a proper workaround either...

 

BTW. (might save someone a few clicks) those properties don't exist jet in at least 2013. So opening the VI in 2011, 2012 or 2013 is pointless.

Message 2 of 5
(2,175 Views)

Thanks.

Didn't think to check that the property existed in older versions - good catch!



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
0 Kudos
Message 3 of 5
(2,172 Views)

The (brown, private) VI Linker Errors returns the VI name, but not the class name. So does the (brown, private) Get Missing Dependencies Information.

 

Label.Text on the SubVI also gives the VI name but not the class...

Message 4 of 5
(2,168 Views)

Useful to know. I also tried them with the missing VIs in a diagram disable structure and it didn't report anything in the Linker errors or missing dependencies (I guess that would be expected as the VIs are not required to execute). I had a situtaion like this the other day which created conflicts, but couldn't find them. The VI still ran without problems.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
0 Kudos
Message 5 of 5
(2,160 Views)