Hello all, I've looked through the forums and not found a solution to this.
I have a very large historical collection of inventor parts, (going back to Inv R5) and need to add data to their iproperties. I can do this en-masse from within Vault. Then, when I open the part (.ipt) in Inventor my iproperty values are present.
All good so far.
The problem is if I open an assembly in Inventor that contains these ipt files. The iproperties I have added don't show up in the assembly files. To clarify, if I open the individual ipt, I get my new iproperties. If I open an assembly containing these ipts, then the iproperties don't appear on the component parts.
This is a problem for me, because I need these iproperty values to appear in a bill of materials table on my drawings.
Refreshing the assembly from Vault doesn't work.
Rebuild all has most of the component items greyed out - not sure why.
Using 'Get' and overwriting the files in my working folder also doesn't work.
Deleting the assembly files entirely and reopening from Vault doesn't work.
Is there an easy way of opening an assembly, and telling Inventor to refresh all the iproperties from Vault? I'm using Inv2020
I feel I'm missing something tremendously obvious...
Thanks
Jon
CAD and PLM admin | My ideas | Inventor-Vault Expert GPT (my AI brain)
Hi, have you tried using Synchronize Properties from Vault Client? Select a file or group of files, not checked out, and then use Options\Synchronize Properties. If the property mappings are set correctly, Vault ill read the property values between the Vault file and the local copy and synchronize them accordingly. I would test it first on one individual file, to see if it solves this for you.
If not, please share a screen shot of your property mapping for the Property that is not updating.
Chris Benner
Industry Community Manager – Design & Manufacturing
If a response answers your question, please use ACCEPT SOLUTION to assist other users later.
Also be generous with Likes! Thank you and enjoy!
Thanks for the replies all. I think the reason it was being weird is that it turns out that none of our assemblies have 'enable bom' turned on. Checking out the assembly, turning it on, and checking it back in solves the issue.
I was really hoping I could do all this as entirely within Vault to save the 'check out check in' hassle, but oh well.
Thankyou everyone for replying!
Jon
Hi! You could make BOM enabled by default. Simply open the iam template file -> BOM -> enable the BOM views -> Save. Next time you use the template to create a new assembly, the BOM views will be enabled automatically.
Many thanks!
Done that now, thanks!- unfortunately there's 20-odd years worth of assemblies in our Vault that are not.. 😞
Can't find what you're looking for? Ask the community or share your knowledge.