5 Replies Latest reply on Jan 28, 2015 9:14 AM by Craig Schultz

    "Drawn By" drawing property is disappearing...???

    Aaron Torberg

      We are experiencing an odd problem - through a certain set of actions we are clearing the "Drawn By" property in our drawings.  Our workflow has an automatic transition at the beginning of the process that applies the "%initials%" value to a variable "Drawn By" for files that have the extension "slddrw".  The field in the sheet format is set to $PRP:"Drawn By".  When a part is saved, checked in to the vault, then a drawing is made, and checked into the vault, the field populates correctly.  If the drawing is checked out, and back in again the drawn by field in the drawing is cleared. The property remains in the drawing file, but it is blank???  This is the only place the variable "Drawn By" is used in the workflow, and a read only field "Drawn By" exists and references the drawn by variable on the drawing data card.  I don't understand how this variable is being cleared without passing through a transition - a check out/check in, clears the property???

        • Re: "Drawn By" drawing property is disappearing...???
          Faur Arama


          How is "Default overwrites" (on drawings file data card) flag on Drawn By variable?

          • Re: "Drawn By" drawing property is disappearing...???
            Craig Schultz

            I have (had) the same problem..  It happened when I create a PDF through tasks, not through a transition.  It used to work fine until we upgraded to 2015.  So what I've done to remedy it was to add the designed by and approved by variables to the model card as well. 


            On another note, it was also clearing the number of sheets variable I had on the drawing card.  I had to remove the $PRPSheet attribute from the variable, and just left it as a custom property going to the SW extensions.


            This seems to remedy the problems in the dozen or so tests I've done.  Lots of head scratching, but I think I figured it out.  Pretty frustrating considering It was working fine since the implementation 20 months ago.