Previously, I documented two new functions related to the new Copy Design app in Vault 2015 R2. Now I would like to explore some uses for those functions. The most obvious usage is to build your own Copy Design algorithm that meets your specific needs. Technically, a custom Copy Design as ...

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.

If you want to update a Vault property and that property is mapped to a value within the file, you have a couple of options, and they both suck. This post is to introduce a third, and non-sucky, option in Vault 2015 R2. Again, I’ll be using the previously undocumented functions from Copy D...

To celebrate the release of Vault 2015 R2, I wrote an app that lets you generate BOM reports automatically through the Vault job server. If you are not already aware, Vault 2015 R2 has a BOM Report feature. From any BOM view, you can run the Report command to generate a report of the BOM t...

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.

If you want to update a Vault property and that property is mapped to a value within the file, you have a couple of options, and they both suck. This post is to introduce a third, and non-sucky, option in Vault 2015 R2. Again, I’ll be using the previously undocumented functions from Copy D...

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

In Vault 2015, PromoteFiles has been removed from the ItemService. Previously, the quickest way was to call PromoteFiles followed by UpdateAndCommitItems. Of course, more complex cases would require more API calls and data checks. Anyway, the simple workflow just got more complex in 2015....

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.

Working Folder is another one of those concepts that is more complex than you would expect it to be. At it’s core, things are pretty simple, you map a local folder to a Vault folder. That way Vault clients know were to upload and download files to. The complexity comes from additional fea...

Update: One of my readers was able to find a link to Visual Studio 2008 Express Web Edition. After that, install the Reporting add-on, and you should be good for RDLC editing. Thanks Alex. So, you want to make custom Vault reports. Good for you. All you need is a Vault and Visual Stud...

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.

Vault uses two different security mechanisms. There is a system based on user permissions and a system based on access control lists (ACL). The permissions-based security is part of the base Vault functionality, but the ACL based security is an optional feature which may or may not be avail...

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.

There was a video posted recently about Vault Office, so I thought I would have an article about API licensing for Vault Office. And while I’m at it, I may as well go over all the licensing rules for Vault 2015. It’s not my favorite topic either, but it has to be done. I’ll try to go quic...

Today my blog turns 6, which is 110 years is binary. To celebrate, I’m going to reveal a couple of Easter Eggs that I’ve slipped in over the years. Specifically, the titles of some of my apps. One thing I love about writing my own apps is that I get to pick the name. An in two cases, I named the app in such a way as to set up a joke. That’s just the type of guy I am. Continue reading

We are still keeping Thunderdome open source for the 2016 release. The app itself can be downloaded from Autodesk Exchange. If you want the source code, it’s provided in the link below. Continue reading

There was a video posted recently about Vault Office, so I thought I would have an article about API licensing for Vault Office. And while I’m at it, I may as well go over all the licensing rules for Vault 2015. It’s not my favorite topic either, but it has to be done. I’ll try to go quic...

A couple of people have been asking for this one. So here you go, Find Orphaned Files for Vault 2015. Also, after my last app, I’ve been eager to post something that, you know, works. Click here for a description of the app. Requirements: Vault Workgroup or Professional 2015 Click here t...

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.

Armed with the new capabilities in the Vault 2011 APIs, I decided to re-design the Recycle Bin application. The result is closer to how things work in Windows. The Recycle Bin is now an actual folder and you delete things by putting them into the Recycle Bin. Also, I bundled in the Restore ...

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?

Vault Mirror holds a special place in my heart. It's the first utility I ever released publicly, and it was one of the first utilities to be featured on Autodesk Labs. It took me only a few hours to write, and I figured it would have a short lifetime. Much to my delight, the utility is stil...

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.

Here are some important things you need to know about the new Vault 2011 feature that allows you to queue up a job on a lifecycle state change. Configuring the system Obviously you need to have the Job Server enabled. So that's the first step. You can enable this feature in the Global admin...

In prior posts, Doug introduced a couple undocumented methods in the Filestore Service and described how you could use them to roll your own copy design. In this installment, I’ll show you how to use them to sync up properties to get rid of property equivalence errors. Continue reading

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.

It recently came to my attention that there are no articles on using the Find X By Search Conditions. So let my fix that now. These Find functions are the API equivalent of the Advanced Find command in the UI. Hopefully you are familiar with the following dialog. The basic idea is that yo...

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.

Project Thunderdome is here for Vault 2015. It’s the same product you have come to know and love, but I’ve made a few improvements this time around. First, it’s been posted to the Vault App Store. So that’s a bit of a status upgrade from previous years. If you are interested in the sourc...

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 was hoping that I could retire DECO now that Vault Data Standard has support for custom objects. Unfortunately, DECO still has one feature that Data Standard does not. DECO overrides the “new” command with custom content. Data Standard lets you create another new command, but the defaul...

I was hoping that I could retire DECO now that Vault Data Standard has support for custom objects. Unfortunately, DECO still has one feature that Data Standard does not. DECO overrides the “new” command with custom content. Data Standard lets you create another new command, but the defaul...

It recently came to my attention that there are no articles on using the Find X By Search Conditions. So let my fix that now. These Find functions are the API equivalent of the Advanced Find command in the UI. Hopefully you are familiar with the following dialog. The basic idea is that yo...

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.

If you are a Vault Administrator using the advanced security features in Vault, you need this app. Period. Here is the video from the 2013 version if you need some background on the app. I didn’t add any new features in 2014. Requirements: Vault 2014 Workgroup / Professional Administra...

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.

Update: Q-Tools 2013 is now available. Note: Click here for Q-Tools 1.0. Here is Q-Tools 2.0. I updated it for Vault 2012 and hopefully fixed the multi-site issues. I also added, by request, the ability to email multiple addresses when errors are detected. Here is the full feature list: ...