I'm sure this has been asked before, but whats the best way to make sure all the data on the part/assembly/drawing cards are all synced? It seems like some tabs fill out information, but other tabs don't.
Make sure you check the Updates all configurations option in the Card Editor for a variable, which you would like to update.
See the attaching image, for more info.
Hope this helps.
This works for all configurations that exist at the time the data is filled in.
"Update all configuration" = Update on change!
If you add a 'Tab' (Configuration) it will use the Default Values for all variables on the new tab until you change the data in each variable on any tab.
I wrote an add-in to handle this, because I couldn't find a way to do it. I force the user to make their card changes on the "@" configuration tab. On check-in, the other tabs are automatically populated with the values from the "@" config. It's not the greatest solution, but at least the data is consistent.
Interesting, how were you able to do that? I don't really know anything about programming.
Without going into too much detail: you can create add-ins using the EPDM API that are triggered by certain events. In this case, I used the datacard save and check-in events to trigger the code. The code then gathers the variable values from the "@" configuration and applies it to the other configurations. It's fairly easy to do if you know how to program, but I would have expected the option for a variable to update all configurations to handle this. In our case, especially with DWG and SolidWorks drawings, we have no need for these configuration tabs. I'm sure they have their place for some users, but with us, all it does is cause confusion and require custom coding. An option to hide these tabs or truely keep them linked between configurations would have been ideal.
We took it a step further and kept the values linked between multiple files with the same part number. For example, if you have a .doc, .dwg, .sldprt, etc. We are item centric, not document centric. So if you change the description variable of the .doc, it also changes the description variable of the .sldprt. It seems like EPDM is trying to move towards an item centric environment option with their "Items", but it still leaves much to be desired in my opinion.
Jeremy is your code 100% reliable? I've had instances where the variables are not copied between configurations. I've had to check out, change a variable's value, and check in again. I'm just curious if someone else has had the same problem.
I have special handling for items and cut-list items.
As far as I know, everything is working, but I haven't put the code into a production environment yet.
Actually I found that a lot of it has to do with the $PRPSHEET attribute as defined in the variables. Once I removed that $PRPSHEET attribute, things seemed to work a lot better.
Retrieving data ...