Data Standards Customization

Data Standards Customization

gconley
Advocate Advocate
567 Views
2 Replies
Message 1 of 3

Data Standards Customization

gconley
Advocate
Advocate

We currently updated Vault, Inventor, and AutoCAD from 2017 to 2019.

We previously had custom numbering with our data standards.  The customization is not completely working with 2019.  We are being told that Vault 2017 has an API code that isn't compatible with 2019 so we need to have our script rewrote in order to accept the customization.   Has anyone ever heard of this?

 

Our problem is that when we create an assembly inside of Inventor and use data sheet to get our custom number, it gives us the next available sequence number, but does not generate the number inside the Vault sequencies like it did in 2017 vault.  So when we go to generate a part for that assembly inside of datasheet, the new assembly number does not show.  We are forced to go to the vault sequencies and manually add the new assembly. 

0 Likes
568 Views
2 Replies
Replies (2)
Message 2 of 3

Markus.Koechl
Autodesk
Autodesk

Honestly, I can't completely follow the workflow but I am pretty sure, that a general migration step has been missing when you migrated the customized configuration. I'd suggest to follow the steps listed as a minimum in the VDS 2019 What's new documentation; it includes migration starting from 2016. I started sharing migration information as part of VDS What's new for 2018 on AKN. For VDS 2018: https://knowledge.autodesk.com/community/article/82776. For VDS 2019: https://knowledge.autodesk.com/community/article/193121.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 3 of 3

gconley
Advocate
Advocate

The Vendor is the one that did the migration, and it was hard to keep up with him.  We downloaded the new data standards, then installed it and then all he did was copy over the 2017 data standard folder and replaced the 2019 folder because none of the customization was working.  We also went in and changed one of the files to show 2019.  That fixed some of the issues, but not all of them.

0 Likes