A few months ago my colleague Mike Space wrote about powerVault – a native PowerShell extension produced by coolOrange that can dramatically simplify interaction with the Vault API. Today I’d like to build upon that idea by illustrating how using powerVault in conjunction with the Vault Data Standard can provide a complete solution for customizing Vault behavior.
There’s a neat ‘trick’ you can perform using Vault Data Standard (VDS) and iLogic that involves creating Engineer-To-Order (ETO)-type components. If you have a semi-standard product line that changes based on customer spec you can use VDS to help create new iterations of those components, and even off-load the creation of those components to non-CAD users.
In a recent article I discussed that starting with the 2018.1 release, Autodesk has included three new means of sharing Vault data outside the company firewall. This article will focus on the second method of sharing data: Pack and Go to Autodesk Drive. This functionality is available starting with the 2018.2 release of Vault.
Topics: Data Management