I was hoping to find others with this issue on the forums. However, searching hasn't returned any results.
I've had Revision mapping setup between Inventor and Vault since we first implemented Vault. It's been working fine until I upgraded to Vault 2014 ADMS a few weeks ago. I've deleted & recreated the mapping between Rev Number (UDP) and the Revision (System prop) and Inventor Vault as per the standard way of doing so. I did this in the hope it would start working again.
Each time I run the Synchronize properties command from within Vault explorer (2013 or 2014) the result tells me no changes are necessary even though inspecting the properties grid clearly shows the properties aren't in sync.
checking the file out from within Inventor confirms the properties aren't in sync and prompts the user asking if they want to update the properties. Selecting yes, does in fact sync them as you would expect. The saem is true if you manually update the properties from within the Inventor Add-in.
As an extra twist when the job processor runs the Synchronize properties commands via a state change transition action, it does so as you would expect.
For these reasons I'm confident that my mapping is in fact correct & that this is a bug caused by the 2014 ADMS.. Not a good sign really. To confirm the behaviour is the same whether I use the 2013 or the 2014 Vault Client.
Has anyone else sucessfully updated to 2014 and their Revision Mapping is working as it was previously in 2013?
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
Solved! Go to Solution.
Solved by mbodnar. Go to Solution.
Solved by mbodnar. Go to Solution.
Same here
Created new Vault in 2014 and had to re-create the mappings between UDP Model Rev No and File property Rev Number which I have had to do for the last 2 Vault releases to get it working.
Then I also created mapping between system property REVISION and File property Rev Number
Vault DOES NOT show non compliance even though Vault Revision equals one value and file property Rev Number is blank.
Also the sync properties does not appear to work. I have to open models in Inventor and use update properties before it syncs properly.
I thought it was broken before as I have had remove all mappings and re-add to get it working, but now it's broken completely. I checked in Vault 2013 and same mappings and works OK, so issue must be with Vault 2014
Regards
Max Bodnar
I hoped that would be the case for me. But it seems it makes no difference.
cheers for sharing.
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
The behaviour might be different between these two options:
Inventor 2013 & Vault Client 2013 with the 2014 ADSM
vs
All 2014.
I'm currently only trying to get it to work with the first option.
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
@mbodnar wrote:
Not sure if this is related, but it appears that when file property is blank, the Vault sync does not work. Once a value is added it starts working
I can confirm this behaviour with Inventor 2013 & Vault 2013 with 2014 ADMS. This wasn't an issue with the 2013 ADMS:
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
Yeah I'd say its specific to the Revision system property being pushed to a null value.
Have you confirmed that if you go from WIP to released, when the WIP rev number is null & the Vault Revision gets bumped up that the job processer sync also fails? This would all make sense if thats the case.
I have a compliance test to make sure the Rev Number property is propagated prior to allowing the transition to take place. Hence why I have been saying the JP sync has been working.
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
@mbodnar wrote:
Not sure if this is related, but it appears that when file property is blank, the Vault sync does not work. Once a value is added it starts working
Also I deleted all Rev Number default mapping and added two new ones, one for Inventor and Inventor dwg as I have found so far that the default mappings do not work
Hope this helps
Cheers
Max
I accepted this as the solution, but it is only a workaround, this is a verified bug. Just waiting for Autodesk to pick it up and escalate it now.
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
Max I've just found this issue as well.
https://dl.dropboxusercontent.com/u/29242712/capture-5.mp4
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.
Design & Manufacturing Technical Services Manager at Cadpro New Zealand
Co-founder of the Grumpy Sloth full aluminium billet mechanical keyboard project
Hi Scott
yes I did notice this yesterday, I was going to use this method to sync could not
So we are stuck using the manual method of opening model in Inventor and update properties
Not very suitable when trying to sync large legacy datasets
Autodesk, any comments?
Max Bodnar
Hi Scott
I came across this the other day. When setting the Create option to YES, it can push the value from Vault into the iproperty especially when value is null. This never used to be the case but it seems to be in 2014
The mapping between the two "Vault Revision" and "Model Rev Number" does not consistently work well out of the box. Autodesk support are aware of this
Max