Vault 2016 Copy Design Part Number

[Anonymous]

I have noticed that there is no way to update the part number for files when using Copy Design.  Am I missing something or is this a bug?

[Senthil_Kumar]

By default File name is mapped to Part Number. With the new Copy Design this is done via Action Rules. Please check the following image on how to do.

Hope this helps.

[Anonymous]

I checked that, it was already set up by default.  I even created a new set of Action Rules that would do this and it still didn't work.  I have read online that other people have had this issue and one person tested it by creating a new Vault and they said it worked then, but it doesn't work when using an existing Vault.

[Senthil_Kumar]

So is your vault a migrated Vault or a New Vault? Do you have any other mappings for Part number?

[scottmoyse]

The default rule also wipes out all your iLogic rules. So watch out for that!

[r.smith1]

Hi Bret,

This is to confirm the issue you have described, and information you have provided to me has been sent to the software development team for further review.  Thank you for promptly sending datasets when requested, it has helped tremendously in reproducing the behaviors you see in your vaults, with respect to what I see in mine.  

[Anonymous · Accepted solution]

I figured it out.  I needed to Assign the Action Rule set and make sure the button was pressed to make it use the new rule set.

[Anonymous]

So, suddenly today we noticed that the part number is no longer being copied when using Copy Design.  It was working for a while and now all of a sudden it does not.  We haven't made any changes to the Action Rules.

Now what could be the problem?

[steveh5]

Still stuggling with this...Finally got our db migrated to 2016.

So...I set up a new rule action rule per the instructions above.... "TEST"

Set the Selected Ruleset to "Test" and made sure the button was hi-lighted.....

Ran a CD of a single file and the part number remained the same as the previous file....

What am I missing?

Not sure if this has any bearing on the issue....but the numbering schemes are not sticking either. Related thoughts? Admin setting? db issue? Create a Support Case?

[olearya]

Hi Steve, 

Likely we are seeing an actual bug here we have found in migrated databases and property settings, looking to provide a resolution to this soon.

[Neil_Cross]

Allan - On face value I think I reported this issue on 01/01/15 whilst I was doing the QA work alongside Jim, it was logged as PDM-2846 / PDM-3832.  At the time it wasn't we didn't establish that it was related to a migrated database, although that's what I was working on, but the QA team reported back that they had reproduced it.  Is this the same issue? It appears to be identical.

[olearya]

Hey Neil, 

I can confirm issue has been reproduced by development.

[Anonymous]

HI Steve,

As far as I can tell you didn't miss anything. I review the videos from Au again, followed the steps exactly, and no part number change. I must say I'm using old data from an Old Vault checked into a new Vault.

Is it possible that it's a file problem not a vault problem. I need to test New data and checked into new vault, will let you know.

It becoming frustrating..

Mb

[scottmoyse]

This has caused no end of trouble for our customers. Another reason to bail on the new Copy Design tool. Frustrating! We are rolling back customers to the old copy design until:

• You can find & replace folder names for copied components like you can in the old copy design (when copying to and creating a new folder structure)
• The default Action Rule is set to preserve data and not destroy it (Currently it removes iLogic rules)
• This Part Number issue is resolved

[Anonymous]

HI Scott,

So are we looking at a Service Patch, Hotfix, or a process posted to blog/discussion soon?

Thanks

Mike B

[Anonymous]

Hi Scott,

My last post may not be as clear as I expected.

The new copy design has caused pain here as well, however rolling back to the old copy design? Did Autodesk supply process or code. I'm not clear as how to accomplish that. In my client cases I tested their data before we made plan to move to 2016 vault, all of them are in a holding pattern at the moment, until , as you noted these issues are fixed.

MB

[scottmoyse]

---

mbaker wrote:

The new copy design has caused pain here as well, however rolling back to the old copy design? Did Autodesk supply process or code. I'm not clear as how to accomplish that.

---

You need to edit the following XML file on each workstation:

C:\Users\<user>\AppData\Roaming\Autodesk\Autodesk Vault Professional 2016\ApplicationPreferences.xml

<Property Name="Use Old Copy Design" Value="True" />

[steveh5]

Gang...

For what it is worth.....

I did a complete uninstall of VP2016 Client and INV 2016 yesterday. Deleted anything in the Program File, Program Data, and user directory that looked like Vault.

Re-installed both.

And....Like magic...

Part Number is working now when you do a CD.

I also did a db restore of our production db to our test server too.

So...it's working, but not sure what fixed it. If it's the db or the UI?

Aaaarrrggg!

[Anonymous]

Hi Scott,

Thanks I will definitely deploy this option...

Mike

[Anonymous]

Hi Steve,

What are your action filters to make the part number work?

Mike B