Currently all IV sheet metal parts have flat pattern width and length as custom iProperties. But we have hundreds (maybe thousands) created before we started adding these properties.
I'm looking to write an IV macro to add these properties to those parts where they are missing to avoid going through the files manually one by one. But since these are in the Vault I need to check the parts back in after after adding the properties i.e. to iterate through a directory Opening - Adding iProperties - Closing and Checking In ?

Is the check in something I can do in the IV macro, or do I have to write a Vault macro which presumably I call from the IV macro? I'm unclear how to proceed with this and would appreciate some guidance.

I've tried the Autodesk Vault forum where it was suggested I use the Task scheduler and Autodesk IV Customisation forum but I thought I'd try my luck here as well.

For checking out some parts, you can use this "Imports VaultAddInLib", for using vault API. This is unsupported by ADSK but I used it successfully in the past. Not sure you can Check-in after programmaticaly.

_________________
Christophe S....t
Dev. App. Eng.

use design Assistant copy properties or Create an vb.net addin or i feel apprentice is best suited for ur case

Would you mind clarifying each of the three methods outlined above, not being too bright tonight.

I have no problem in iterating through a directory, creating custom iProperties and adding values, it's just I end up with a load of checked out files
(and no, ditching the Vault is not an option)

For Design Assistant
http://www.youtube.com/watch?v=6WiC-1JVjsk

but if custom properties is a function then it wont work

vb.net
do u have Microsoft Visual Studio 2008

if yes,
i will give u the code ,
paste it and debug

or u can find more information on Brain Ekins "mod the machine" - blog

While normally I use VBA/VB6 with Inventor, I do have a copy of VS2008 so any code to illustrate how to check files into the Vault would be much appreciated.

Thank you.

Hello,
What happens to sheet metal parts of you perform a Migrate on them? If Migrate with say, full rebuild creates these properties, then I'd think about building a Sequential Task from Task Scheduler, Check Out, Migrate and then Check In.

I've no way of testing what I've just said.

HTH

Scott

According to the Task Scheduler help files


To create the custom iProperties I need to run the macro so it picks up the property value from the part flat pattern.

I'm rapidly coming to the conclusion that I have to process one directory at a time, then manually run Task Scheduler to check in all the files saved in the corresponding local directory.

I admit I'm not an Inventor expert, much less a Vault expert (having kept well away from the Vault in the past). But I'm surprised that while there is an API for Inventor and an API for the Vault there seems no way to "join the two together"? Or maybe I just haven't found the one person in the world who knows how to do it.

It doesn't look as if you can automatically "force feed" Task Scheduler with the task you want it to carry out (check in files) and, in my case, the directory I want to be checked in.

I can't believe that someone hasn't faced this problem before.

This is not exactly true. Basic Vault's API have no official existence. The only supported API are for Vault for Workgroup, Vault Collaboration and Vault Professionnal. I received a training last month about these. IMO using the Task Scheduler for check-in is a great idea because you can only do a check-out programmaticly.

_________________
Christophe S....t
Dev. App. Eng.

Apologies for lack of precision.
For "Vault" read "Vault Manufacturing 2010".

Oh! Let me few days. My training was about Vault 2011 Professionnal.

_________________
Christophe S....t
Dev. App. Eng.

Who told you that? Basic Vault does have an API, and it is supported.

_________________
Doug Redmond
Software Engineer, Autodesk Inc.
http://justonesandzeros.typepad.com/