The post after this one has a sample project: http://justonesandzeros.typepad.com/blog/2015/02/another-way-to-update-properties.html

1. Have a look at these articles if you haven't already. For some background on how "Vault SQL" properties and file properties work: http://justonesandzeros.typepad.com/blog/2010/06/properties-in-vault-2011---part-2.html For sample code on finding the moniker: http://justonesandzeros.typepad.com/blog/2010/07/properties-in-vault-2011---part-4.html 2) Are you talking about unmapped properties? Properties that just live in Vault and not the file? Yes, those are easier to update. You can just call DocumentService.UpdateFileProperties on the files. No need to download or copy the file. However, I think you still need to checkout/checkin the file.

Here is the answer I got back from the Vault team: "GetLatestItemByItemMasterId would be my guess." If that doesn't work, I suggest logging an ADN ticket. Sorry about that.

So you basically want your own version of Copy Design. Have a look at this article: http://justonesandzeros.typepad.com/blog/2015/02/roll-your-own-copy-design.html In the last step, AddUploadedFile(..), is where you specify the references to any child files. You will need to look at the relationships of the original files and make sure to set things up the same way for the new files. At that point you should be good. Internal references are fixed up on download. So when you call AcquireFiles, the Vault framework will edit your local copy to point to the new file.

Have a look at this article: http://justonesandzeros.typepad.com/blog/2014/04/disabling-and-enabling-bom-rows.html If that doesn't solve the problem have a look at this article: http://justonesandzeros.typepad.com/blog/2014/05/component-bom-rows.html

You should post this issue on the Vault Customization discussion group. http://forums.autodesk.com/t5/vault-customization/bd-p/301 Blog comment sections are not a good place to post code snippets. Also, there are more people reading the discussion group.

I'm pretty sure there is a way to do it. I think you have to set filters on the table or something like that.

The recommended approach is to use lifecycle states or Folders to manage security. Setting ACLs on each object can be difficult. If you think you need to do security on an object-by-object basis then it depends on what you want. If you everything to have the same security and you want to be able to update them all together, then sharing an ID is a good idea. If not then, you are forced to have a different ACL ID for each object.

Here is what I have been able to find out... Yes, you can develop a plug-in to the Vault Office client. However, you are supposed to limit the functionality to be in-line with the Vault Office features. You can contact Younes Yammouri (younes.yammouri AT autodesk.com) if you have functionality questions. If you are developing your own EXE that talks to the Vault Server, then your app will consume a Workgroup or Professional license. You can't write a stand-alone app that uses the Vault Office license.

Development is allowed on Vault Office 2016 client, but you need to stay within the Vault Office feature set. I'm trying to hunt down some "official" documentation on this topic.

Sorry, I'm not on the Vault team any more and don't have time to keep all my Vault apps current. The source code is available, so it's possible that someone will come along and update this app.

It looks like I left out a project when I uploaded the source code. You can download the missing project from here: http://justonesandzeros.typepad.com/Apps/JustOnesAndZerosWebServices/JustOnesAndZeros.WebServices.zip.abc Remove the extension ".abc" and unzip. It should have all the missing source files.

I'm not aware of any case sensitive issues. Vault Mirror shouldn't care about file type. My guess is that it's something else. Is Vault Mirror writing to a log file. Is there anything in there about the files? Are there any security restrictions? Log into Vault Explorer using the same user that Vault Mirror uses. Can it access all the needed files? If you download the files through Vault Explorer, are there any issues?

Hey Matt. I get alerts when new comments are posted, regardless of how old the post is. Anyway, one possible solution is to not use JobProcessor, which handles one job at a time. I have another post describing how you can build your own service to read jobs off the queue. This allows you to get around the limitations of JobProcessor. http://justonesandzeros.typepad.com/blog/2013/02/custom-jobs-without-job-processor.html For example, your service could reserve 50 jobs at a time, process them all together, then mark the 50 jobs as complete.

This blog is not a good place to post and debug source code. There is a discussion group on the Vault API: http://forums.autodesk.com/t5/vault-customization/bd-p/301 I suggest you post the issue there. Not only is it easier to read, but more people are active on the group. You should be able to find help for you issue in the discussion group.

According to the store page, Project Thunderdome 2016 works with Vault Workgroup and Professional. https://apps.exchange.autodesk.com/VLTC/en/Detail/Index?id=appstore.exchange.autodesk.com%3avault2015projectthunderdome1428957288_windows32and64%3aen Vault Basic doesn't support plug-ins to the Vault Explorer client, which is why you need Workgroup or higher.

Thanks. I miss Vault too. I'm still at Autodesk, so you'll probably see me around next time I have a product that I can blog about. Autodesk Developer Network fully supports Vault. There is also a discussion group on Vault programming that's run by the Vault development team. http://forums.autodesk.com/t5/vault-customization/bd-p/301 So that part is covered. The main thing missing is somebody to take over blogging and sample apps. But I still prod the Vault team whenever I get a chance.

I'm not on the Vault team anymore, so I'm not updating any of my apps. Hopefully, Data Standard can provide all the features you need.

Use FindLinksBySearchConditions to search for links. If you want to find Files and Links within a folder, you will need to make 2 API calls, one for Files and one for Links.

The "Changes" page in the SDK docs should tell you what to use for removed functions. I apologize if this was not done. GetUseACLForItemLifeCycleStates is no longer a global setting. You can read the StateBasedSec value off the LfCycState object. Call LifeCycleService.GetLifeCycleStatesByIds to get the lifecycle state object. GetItemLifeCycleStatesACL has been replaced with LifeCycleService.GetStateACLByLifeCycleStateId.

It should be fairly easy to update this app since it's not a plug-in. Here are the basic steps: 1. Download the source code. 2. Open the project in the latest Visual Studio version. 3. Set the references to the 2015 or 2016 Vault SDK DLLs. 4. Fix any compile errors that may arise from changed APIs. See the "Changes" pages in the SDK documentation.