Copying Files from Directory Into Vault
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi guys, got a pickle at the place I work. We're attempting to move into vault from a Windows Explorer (drive) based file storage system. We'd been working with our Inventor support group to get all of our files into the vault, submitted CAPEX to our higher ups, etc... however they're starting to ask some questions that make me wonder if they'll actually approve the CAPEX because we have over 500,000 files and they may just tell us move the stuff you're working on into the vault on a project by project basis. Some of our machines are massive so saving each file into the vault by itself is going to be a fools errand however it's something I can program my way out of - the catch here is that I'm not 100% certain what I'll need to do when copying the files in.
Currently all of our files are saved to a multi-user project (folder/file/template?) - so let's say I have a vault project template (single user - I assume this is standard for vault) and the current project template which is shared. If I save a file located in the Windows Explorer drive to the Vault location on my C: Drive - (the default place where vault will work out of in the future) will there be an issue with the project file/folder templates?
I guess what I'm wondering is, theoretically, can I run the SaveAs on AllReferencedComponents, have the script replicate the folder structure from our Windows Explorer drive, and expect to be able to check in files as well as open things without issues from the Vault Project Template? Or will there be a lot more involved?
Secondly someone in the past created a ton of iPart factories for our bolts, screws, etc... is it possible to anticipate any complications copying in/over iParts?