Hello
I haven't found a similar topic, please redirect me if a topic already exists and sorry for the duplicate.
I'm having an issue with values propagating in drawing cards when copying. On the drawing card, the variable is read-only, because it is retrieved from the 3D via $PRPSHEET. I notice that only the "@" tab retrieves the 3D info, and that the other tabs keep the values of the copied part despite "Update all configurations" being enabled. For your information, the tabs of the sheets ("Sheet1" in my case) are filled in on the copied part because the StarterPack recovery procedure requires this via DataRecovery.
This is very annoying, because there is fake info in the "Sheet1" tab, and this info seems to be used randomly in the explorer, in searches, in the PDM pane of SolidWorks, etc. So it's not clean and it bothers me.
To try to get around this, I changed the setting of the drawing board. I choose to replace the default and delete the existing value. In this way, during an archive, the drawing card is filled in via $PRPSHEET. This works by copying and pasting into the local view (CTRL+C, CTRL+V), but does not work by using the "Copy Tree" tool. It seems to completely ignore everything that is set up in the map.
I did a bit of digging and it seems that you can set the behavior of the "Copy tree" function, but all my attempts don't work.
I attach a pdf for more clarity.
Thank you in advance for your help.
pdm_-_copier_larborescence.pdf
Hello
You should contact your reseller because to my knowledge the cards associated with the slddrw files have a particular operation (or rather a bug) because the sheets do not have custom properties associated in the file.
It's purely a map display. From memory, there must also be a change on a drop-down menu for the propagation to be done from one tab to another of the map.
The random display in the vault interfaces is also a bug as far as I know. Normally, according to SW specs, the vault displays the variables of the last modified configuration. At home I have never seen this behavior and it does not display the same thing between the search results and the windows explorer. For the drawings, on the other hand, it's totally obscure.
Hello
Thank you for your answer. The reseller asked me to open a support ticket because he didn't have a solution. I regret that I didn't test all these behaviors better during the StarterPack implementation phase.
I noticed that the propagation happens if I remove the read-only attribute: if I force a value in a drawing card, the data propagates on all tabs. On the other hand, when the value is inherited from 3D, only the "@" tab is updated on the drawing board. And it's very annoying because the goal is not to have to re-enter the values on the drawing cards. Apparently this behavior has been changed on the 2019 version (I'm in 2018).
What I find very strange and impractical is that the behavior between a copy and paste and a tree copy is not the same. It's incomprehensible to me that the tree copy doesn't take into account the configuration of the maps (replace the default, etc.).
I'm in the process of overcoming all these problems via transitions. I "clean" my cards during the first transition. For example, for my problem with residues following copies, I delete the values of the drawing cards, and then I fill only the "@" tab by retrieving the variables from the 3D (see screenshot attached, I chain the 2 actions and this for all the variables that cause me problems). So I end up with an important list of actions, but at least the maps are clean and I don't have the risk of finding erroneous values everywhere (searches, Windows explorer, SW pane, etc.).
Thank you
capture.jpg
1 Like
Hello
The problem is that Solidworks PDM has just as many bugs as Solidworks. Note that the first version dates from 2009 if my memory is correct and that there is a lot of room for improvement to make the behavior more reliable.
For example, some settings applied to a group don't apply to users in the group. You have to set up the user directly, which is contrary to the nominal operation of a group setting. So that there are differences in behavior between a copy/paste and a tree copy doesn't bother me that much:)
Hello @ cthievent ,
I am very interested in your subject and the solutions you propose because I noticed the same problem as you with the 2018 version, unfortunately I did not have the time to devote it.
Kind regards.