AnsweredAssumed Answered

PDM tasks not writing variables to file name correctly

Question asked by Grant Kirkland on Jan 13, 2020
Latest reply on Jan 15, 2020 by David Lane

Like • Show 0 Likes0
Comment • 11

I'm trying to set up the PDM 2018 task to convert SLDDRW to PDF and SLDPRT to STEP via workflow transitions. However, the tasks are not filling in the description field of the file name correctly.

I want the output file name to be PARTNAME-CONFIG-REVISION, DESCRIPTION ie: "Part1-00-A, Base Plate"

As you can see from the attachment, instead I am getting "Part1-00-A, %Description%". What is causing the "%...%" ?

As for the STEP files I'm getting no description at all, ie: "Part1-00-A, .step"

Has anyone run into this problem before?

Attachments

Capture.JPG70.7 KB

No one else has this question

Outcomes

11 Replies

David Lane Jan 13, 2020 12:42 PM
Mark Correct
Correct Answer
Add a screenshot of your task "Output File Details"
Like • Show 0 Likes0
Actions
- Grant Kirkland @ David Lane on Jan 13, 2020 12:56 PM
  Mark Correct
  Correct Answer
  Like • Show 0 Likes0
  Actions
  - David Lane @ Grant Kirkland on Jan 13, 2020 1:06 PM
    Mark Correct
    Correct Answer
    Did this work before and stop working after an upgrade?
    
    Click "Advanced Scripting Options..." and then "Reset..."
    
    Otherwise, I believe it is trying to use the variable from the new file. You would need to ensure you are mapping the source "Description" to the destination "Description", and also ensure the variable is on the data card for the PDF/STEP files.
    Like • Show 0 Likes0
    Actions
    - Grant Kirkland @ David Lane on Jan 13, 2020 1:11 PM
      Mark Correct
      Correct Answer
      I just posted an update, it looks like it only pulls the variable from the original file's configuration specific property.
      Any idea on a workaround?
      Like • Show 0 Likes0
      Actions
      - David Lane @ Grant Kirkland on Jan 13, 2020 1:16 PM
        Mark Correct
        Correct Answer
        Assuming you want the same description for each configruation... For the source file you'd need to check the "Updates all configurations" box in the data card editor for Description. You'd also need to make sure your users are only changing the description on the data card and not in the custom properties command within Solidworks.
        
        Otherwise have your users set the description for each configuration, while leaving the "Updates all configurations" option unchecked.
        Like • Show 0 Likes0
        Actions
        Grant Kirkland @ David Lane on Jan 15, 2020 10:34 AM
        Mark Correct
        Correct Answer
        If I had a nickel for every time config specific properties have thrown a wrench in things... So here's the thing, if a part has multiple configurations then the config specific fields are filled, if not we use the custom properties fields.
        This has always seemed to make since, as if we were to always fill data in the config specific properties regardless of number of configs then custom properties becomes obsolete.
        
        Would it be possible to modify the existing task to be something like "if config specific field is blank then fill from custom properties"?
        Like • Show 0 Likes0
        Actions
        David Lane @ Grant Kirkland on Jan 15, 2020 11:10 AM
        Mark Correct
        Correct Answer
        Grant Kirkland wrote:
        
        If I had a nickel for every time config specific properties have thrown a wrench in things... So here's the thing, if a part has multiple configurations then the config specific fields are filled, if not we use the custom properties fields.
        This has always seemed to make since, as if we were to always fill data in the config specific properties regardless of number of configs then custom properties becomes obsolete.
        
        Would it be possible to modify the existing task to be something like "if config specific field is blank then fill from custom properties"?
        I'm sure it's possible; however I don't know what code you would need. In your screenshot above if you click "Advanced Scripting Options" then you can modify the vba code.
        Like • Show 0 Likes0
        Actions
        Grant Kirkland @ David Lane on Jan 15, 2020 12:17 PM
        Mark Correct
        Correct Answer
        <VarReplacerScript>
        localConf = conf
        If conf = "" Or conf = "All sheets" Or conf = "All" Then
        localConf = "@"
        End If
        resultFileName = convFileName
        Looks to me like this should be pulling from the @ tab if no config specific properties. Doesn't seem to be working...
        Like • Show 0 Likes0
        Actions
        David Lane @ Grant Kirkland on Jan 15, 2020 1:27 PM
        Mark Correct
        Correct Answer
        This is just a guess. I am new to vba inside of Solidworks, and don't know what exactly is driving the value of "conf".
        
        I believe it is deciding to use configuration values or file values based on the options set in the conversion settings page of the task. I don't believe it has anything to do with if the values are blank or not.
        
        Meaning, if you have it set to "All configurations" it will use the value from the specific configuration.
        
        I'm guessing you'll want to add something in this highlighted area to check if the config value is blank, if it is then get the value from the file level.
        
        Maybe someone else here, with more vba experience, can provide more detailed guidance.
        Like • Show 0 Likes0
        Actions
Mario Zahren Jan 13, 2020 12:48 PM
Mark Correct
Correct Answer
Is there any Variablename "Description" inside your Datacard?

Try adding "var_" (%var_description%)
Like • Show 0 Likes0
Actions
Grant Kirkland Jan 13, 2020 1:08 PM
Mark Correct
Correct Answer
Looks like it only pulls from the configuration specific field. Is there a workaround for this?
Like • Show 0 Likes0
Actions

PDM tasks not writing variables to file name correctly

Attachments

Outcomes

Related Content

Recommended Content