So I have a situation where I want to build up a polymorphic VI to handle a bunch of numerics, strings, or Booleans. For the numerics, I created a malleable VI so the core is the same. I set the vim to be private to the library. But when I try to build my PPL, I get an error stating "The top-level library you specified contains an exported malleable VI." But I don't. The malleable is private, so it should not be exported. I abandoned the library, just making the cases I absolutely needed and duplicated code and it build just fine. So a few months later, I came back to this library. After some experimenting, I discovered that the PPL will not build if the private VIM is in a virtual folder. It does not matter if this virtual folder sets the access or not. VIM in virtual folder causes an error.
NOTE 1: I discovered this bug in 2019 SP1, but the example project is in 2020.
NOTE 2: My exact situation puts the VIM in a class inside of a library. If the VIM is at the top level of the class, the build will work. So I do have a work around, but it does hurt my project organization.
So in summary...
This causes a build error:
This does not:
I confirm that the bug exist in LabVIEW 2020 f0 and that moving the vim outside the virtual folder the PPL builds ok
I can confirm that this behavior still exists. Has there been a bug report to NI on this?
Just played around with this bug with LabVIEW 2020 SP1 and it appears to have been fixed! It did not show up in the fixed bug list, but I'll still gladly take it.