When trying to pack and go a file from File> Pack and Go, it won't allow me to edit the Save to Name or the Save to Folder. The Select/Replace button also doesn't work. If I try the pack and go from Solidworks explorer, everything works fine but the pack and go from the model won't let me do anything from except add a prefix or suffix. Anybody know why that may be?
Using Solidworks Professional -2018 SP4.0
I don't remember seeing anyone report an issue like that here, and I've not seen it either. You might need to get your VAR involved.
Are the fields/button greyed out or just not working? Can you attach a screen-shot?
Just not working...It only seems to be an issue in a part file.
The fields and buttons when doing Pack and go from an assembly model still function. This may be an issue I should report to our VAR.
Hi Taylor, you have to double click on 'Save To Name' or 'Save to Folder' to modify it. Simple click on 'Browse' to change folder.
I always used the Browse button rather than 'Save To Name' and 'Save To Folder'. Never had issues.
I know. That's what I was doing. I think Glenn was right and I need to forward this along to our VAR.
Hello,
For more info to your VAR, does PnG work when you open the drawing only?
Also, for the Save to Folder, does the Browse button work? (I'm assuming you meant double-clicking the listing, not clicking the button, for this.)
Kevin
Everything functions if I pack and go from the drawing so at least thats a way around having to use Solidworks explorer for now.
And yes the browse button works, but the select/replace doesn't and neither does double clicking any of the fields.
Hi Taylor
I've been having the same problem since updating to SW2019.
This gets all the buttons in pack and go working.
Just had this same problem, but within an assembly file. This worked for me. Thank you.
I have been fighting this since 2018, even more since April when we went to 2019. My only fix was a re-boot. This is much easier. Thanks, Stefan!
You should try to unckeck « lnclude custom decals »
will do
No. Stefan Dodd's answer, above, works perfectly as a work-around, though.
I don't remember seeing anyone report an issue like that here, and I've not seen it either. You might need to get your VAR involved.