IMHO the whole workflow is in dire need of a total re-think as the current iteration is completely unusable unless you're a one-person-shop.
Following is a suggestion I posted on the Ideastation. I'd rather not see it get archived (not added to the roadmap for future versions) due to lack of community support so I'm here to ask for some votes.
Some background information:
The reason the current workflow requires you to import your subassembly on every PC that will view a dwg file using that SA is that the SA actually contains VisualBasic code (programming). Windows security requires VB code to be installed at the system level which means that it has to be added to every PC.
https://forums.autodesk.com/t5/autocad-civil-3d-ideas/sac-within-c3d/idi-p/5580901
Don Ireland
Engineering Design Technician
There's also the issue with the current workflow setup is that help files for custom subassemblies have to be CHM files, but CHM files cannot be used from a network due to Microsoft's idiotic stance that CHM files from a network are a security risk while EXE files aren't. This makes distributing a subassembly for multiple users even more difficult as the help file(s) needs to be installed on every machine. Keeping that up-to-date for every user is nigh impossible for a large firm.
I agree with you 100%. And to add to that issue: when you are selecting the help file, one of the options is to use HTML file. I made an HTML file and attached that to my custom SA. My help file doesn't show up with the SA. 😞
Don Ireland
Engineering Design Technician
Bump. Still looking for votes.
Don Ireland
Engineering Design Technician