-
Re: Why do the tabs in data cards store different information?
David, if I'm understanding the question right, the tabs you are refering to are for the overall file and configurations. The "@" tab is basically the overall file custom properties, the other tabs are configuration specific. If you're not used to dealing with the differences you can easily add information not where you want it. Some screen captures might help.
JM
-
Re: Why do the tabs in data cards store different information?
You are correct with your understanding. I'm looking at these two different "tabs" which seem to be storing different information for the same part. Not sure what else to share for screenshots which shows my obvious lack of understanding. Hopefully this helps?
-
Re: Why do the tabs in data cards store different information?
The named tabs refer to each configuration in your model file. The '@' tab refers to the document level. They are equivalent to the tabs in the custom properties dialog inside SOLIDWORKS:
The 'Custom' tab is the '@' tab. The 'Configuration Specific' tab is for the active configuration. The configuration specific properties will override the document level properties when shown in BOMS, linked to notes and such. You can prevent (somewhat) inadvertently putting data in the config specific tab on the data card by disabling the 'Set focus to active configuration' option in your Display options:
-
Re: Why do the tabs in data cards store different information?
And if you only use configuration specific properties, then turn on the "Hide the @ configuration" option.
-
Re: Why do the tabs in data cards store different information?
This is helpful, thank you.
What is the difference between the "@" and "Default" cards?
-
Re: Why do the tabs in data cards store different information?
The "@" tab is just the whole document (the custom properties for the file itself). The default tab is specific to that configuration like how Jim described above. Configuration specific properties will over-rule file properties. I would not hide the "@" tab unless it is completely understood what it is going on with the files. Also remember that this information is coming from your SQL database not directly from the solidworks file, so sometime you have to check the file in before the card will update, or if you have the file checked out (which you should to do any edits) and edit the data card you still have to check in that information. It can be a little confusing at first, reach out to your VAR for help too.
JM
-
Re: Why do the tabs in data cards store different information?
All SOLIDWORKS part and assembly files have at least ONE configuration in them and it's always been named 'Default'. There is no such thing as a part/assembly file with no or zero configurations. This behavior then carries over to PDM.
You could adjust the name of this single/only configuration in your part/assembly template to something other than 'Default' if you wanted as well.
-
-
-
-
-
Re: Why do the tabs in data cards store different information?
I think it is insane to have the default tab on a file that only has one configuration. If there is only one configuration there should be no different between @ and Default so default should not be there.
The have the ability to dynamically add tabs when you have more configurations so it should be a piece of cake to make it so that the default tab could be turned off for no config parts.
-
Re: Why do the tabs in data cards store different information?
David, one more thing.
If you and engineers in you company are not using specific values for configurations, you can ask you PDM Administrator to change configuration of datacard and choose that every change of value of variable in the datacard will update all values for each configuration.
In other words, if you change i.e. 'description' in @ tab the every another tabs will have updated value for 'description' too.
Regards,
Kamil
-
Re: Why do the tabs in data cards store different information?
David,
You can program the data card with vendor and then the vendor #. I doing this it is possible to make it so no one can put in the same #for that vendor twice.
Dan
