Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

File Property mapping; Basics

3 REPLIES 3
SOLVED
Reply
Message 1 of 4
CAD-One
810 Views, 3 Replies

File Property mapping; Basics

Guys,

I know these are basics. But, I want ot be very clear about them. I am asking those little things that I didnt follow.

Please have a look at this video. Its about mapping file properties with vault data.

 

http://www.screencast.com/users/PS_DM_Bloggers/folders/Media/media/70904eb1-3ec2-4e25-9286-959e4bc3f...

 

@45 secs : you can see that a file from with in the vault is selected. Question is what is the critia for selecting this specific part file. Will all the inventor files have this propery in common. IS it possible that few files might miss this property?

 

@ 50 secs : I understand that the arrow indicates the source and the destination. Buts whats the significance of the create. In some cases, I have create, but in some No. Can some one share the benefits.

 

@1:12 sec: the Update properties is used. Could we have also used Action -> Sync properties? Are these both same commands?

C1
Inventor Professional 2020
Vault Professional 2020
AutoCAD 2020
3 REPLIES 3
Message 2 of 4
Richard.Rankin
in reply to: CAD-One

Hi C1,

 

@45 Seconds; The process is to map the Vault System Property "Revision", in Vault first. In the video "Revision" is mapped back to the Inventor iProperty "Revision Number". To answer your question, it SHOULD map back to all Inventor .ipt, .iam, .idw, .ipn file types. The only situation where I am not 100% sure that it will happen is if the file you are trying to write back to, has not been migrated to the version of Inventor used to create the original mapping. So say you set it all up using Inventor 2011 and Vault 2011, I am not sure if it will write back to an unmigrated Inventor 5 file for example.

 

@50 seconds; The "Create" Yes\No option will create the property in the for you in the file itself. So for example if you wanted to force all files to have a property called XXX. This is not a standard property for Inventor filetypes and so if you switch this to Create=Yes, a Custom iProperty would be created in the file automatically, when you Update Properties in the Client Application. There are some file types that might not work, if they dont support Structured Storage. Examples might be .txt, .tif, .jpg (not a definitive list). However, it should work for most Autodesk Native filetypes and Office Documents.

 

@1:12, The Synchronize Properties command will update the properties in the linked visualization file (DWF), if there is one. It won't edit the original file itself. You must do the Vault>ClientApp>Vault round-trip, and Edit the file in the application editor, hit Update Properties, then check the file back into Vault.

 

I am pretty sure that answers the questions but waiting for someone else to chip in to confirm\rebutt Smiley Very Happy



If you find my response solves your question, please click the "Accept Solution" below the response

Richard Rankin
Vault Support Specialist
Global Product Support
Autodesk, Inc.

Message 3 of 4
CAD-One
in reply to: Richard.Rankin

Richard,

 

Thanks for clarifying my questions.

C1
Inventor Professional 2020
Vault Professional 2020
AutoCAD 2020
Message 4 of 4
scottmoyse
in reply to: Richard.Rankin

here we go Richard with my contribution Smiley Happy

 

I agree with the 45 seconds answer.

 

the 50 secs one i'm not so sure about. I have been wondering about the exact intention of the YES/NO option under property mapping for some time, since its nots in the help file or on the wiki. Logically I assume it does what you say it does. However, I suspect it only creates the property (if set ot Yes) on the files which are assigned to the category the property has been assigned to. Although in a way it is weird; surely if you are mapping a property to a file, then there should be no question about if it should be created or not, you wouldn't be mapping it otherwise....I'm fairly sure I have a number of mappings where its set to no, but it still works. Now this may be because i have created all the Vault properties already in our Inventor & office templates. Maybe the Yes/No would come into play with unmigrated files....

 

I have discussed this Yes/No option with both of the main support guys at my reseller and we are all a little confused by the exact nature of this option, due to the number of ways it could be interpreted and the lack of explanation in official autodesk documentation.

 

Regarding 1:12, I either misunderstand your explanation or disagree with it. I'm fairly certain that Sync properties in Vault explorer does edit the file itself ultimately. It may not until the file is checked out, but it syncs the Vault property with the file property in the database, whether or not it modifies the file immediately or marks it to be modified by the Vault add-in on open i'm not sure. The properties associated with a CAD file & its vault database entry aren't linked to its visualisation file, based on my understanding, I think the only link that exists between a Vaulted file and its visualisation file is the version.

 

So IMO the update properties command in the add-in behaves in a very similar manner to the sync properties in vault explorer. Also the update properties command is the same as the message you get when checking out a file from vault via the add-in, "do you want to update properties, Yes/No"


Scott Moyse
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.


EESignature


Design & Manufacturing Technical Services Manager at Cadpro New Zealand

Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report