CAD Forum

VicFrauenfeld wrote: ↑Thu Oct 21, 2021 2:09 pm Sorry I cannot answer your question. But you say that it is easy to add the part number to the copied or branched file. How did you accomplish that?

File name without extension

bnemec wrote: ↑Thu Oct 21, 2021 2:19 pm There's a way to do it for any data card variable by adding extra (likely hidden) data card variables that are duplicates of the part number and revision for example. Then on CopyTree or Branch (can also be used to help make metadata correct in a Merge I think) you can set data card variables by user group settings. I had started this to have the supersedes data like you mention, but got bogged down and other squirrels ran by and I've not gotten back to it.

The trick is getting the timing right between using proper default values for the variable control on the data card (affects all new files) which IIRC over writes the existing data when copying a file. Then in our workflow all CAD files enter the workflow through an initiated state just for the sake of an automatic transition to WIP that we can set filters and actions on. So data card variables can be set here as well. Again, IIRC this is where the duplicate part number and revision variables come in because they were not changed by default values. I wish I could remember the exact process. Maybe I should just keep quiet until I find my old notes...

berg_lauritz wrote: ↑Thu Oct 21, 2021 3:35 pm So you insert a state after copy tree/branch? How do you do that? Am I slow on the uptake here?

bnemec wrote: ↑Thu Oct 21, 2021 5:46 pm
There's also the user/group settings for Branch CopyTree where you can set variables to some values, I don't know that you can pull data card variables here though.

bnemec wrote: ↑Thu Oct 21, 2021 5:46 pm Bad description on my part. That state is not specific to CopyTree or Branch; any new file that goes to that workflow when added to the vault goes to this state. CopyTree and Brach create new files in the vault just like Save from SW.

image.png

That "Initiated" state is the one in the workflow that has "Initial state" checked:
image.png

I mentioned this because I know that's not unique to our setup and which ever operation edits the data card variable last wins.

So there's the Default Value set according to the Data Card Editor.
image.png

Then any transition(s) that the new files go through when added to the vault that might have an action to set the variable.

There's also the user/group settings for Branch CopyTree where you can set variables to some values, I don't know that you can pull data card variables here though. In screen shot you can grab the source filename without extension for example. in our case that's just a serial number, not part number, so of less help. Thing is, I don't know off the top of my head when this action happens. I want to guess that it's before the file is added, so it's before the default value from data card editor but don't take my word for it. I'm just trying to explain that if a variable is being set in more than one place, the last one wins.
image.png

I hope this is helpful.