Versions Affected: VIPM 2020.2 and older
Fixed in Version: VIPM 2020.3 (not yet released)
When trying to build a VI Package, if the VI Hierarchy of the package source contains any VIs stored under the <LabVIEW>\help folder, then an error dialog (like the one below) will appear, stating that there are missing VIs.
In the example above, the VI "Show in File System.vi" calls a VI "Open URL in Browser". This VI is stored at "<LabVIEW>\help\_browser.llb\Open URL in Browser.vi" (which is under the "help" folder, and is what is triggering this bug).
The workaround for this issue is to not statically call any VIs that are saved under the "<LabVIEW>\help" folder (or call any VIs that have them in their hierarchy).
The best way to do this might be to call the offending VI by reference. You can do this as follows:
Open a strict VI Reference and use a Call by Reference in your VI Package source code (so that there is no linkage to the offending VI), as shown in the example below.
Note: You might be tempted to use a Static VI Reference (e.g. to make it easier to get the VIs path), but this will likely result in a link to the offending VI that will produce the same "missing VIs" error. So, avoid the Static VI Reference and just hard-code the path to the VI.
Example: Show in File System - Proxy.vi