griffindore Posted April 24, 2014 Report Share Posted April 24, 2014 Hi JKI, I built a package where I specified a password on a subfolder by unchecking "Use Protection Settings of Parent Folder". This particular folder's destination is still set to "Use Destination of Parent Folder" which is installing to "Toolkit VIs" set to "Directory (Preserving hierarchy)". The problem is that when this package installs, the subfolder that got a password applied does not go into a location that is consistent with "Preserving Hierarchy". Instead it installs into the root "Toolkit VIs" directory. Not specifying a password results in correct directory installation. Any help would be appreciated. -Mike Lyons National Instruments RF Systems Engineer Update: Using VIPM 2013 SP1 Link to comment Share on other sites More sharing options...
Ashish Posted April 25, 2014 Report Share Posted April 25, 2014 Mike, I was unable to recreate the behavior described by you using my test package. Can you share the packages source? If not, can you create the test package that recreates the behavior and share with us? You can send that info to us on "support@jki.net" to continue this discussion. Link to comment Share on other sites More sharing options...
griffindore Posted April 25, 2014 Author Report Share Posted April 25, 2014 Can you share the packages source? If not, can you create the test package that recreates the behavior and share with us? You can send that info to us on "support@jki.net" to continue this discussion. Done. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted April 29, 2014 Report Share Posted April 29, 2014 We've confirmed this is an issue with VIPM. We'll release a fix in the future for this. In the meantime, the workaround is to uncheck "use destination of parent folder" then specify a custom destination which fixes the destination that VIPM misplaces. Link to comment Share on other sites More sharing options...
Ashish Posted April 29, 2014 Report Share Posted April 29, 2014 Mike, We have recorded the issue as Case 15964 for consideration to be fixed in future release of VIPM. In the mean time, please use the workaround mentioned. We will certainly notify you when we have the fix ready. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.