You can use the design table and excel intelligence to get the desired results.
This is more of a philosophical answer regarding part names, part numbers and revision numbers.
I like having a unique name for reach part file. and I use Property Tab Builder to assign the official part number and Revision code.
These properties are configuration specific. This allows one part file to have several sizes that can be controlled by a design table.
Same idea for assemblies. Each configuration can have its own part number.
By having the file name set as "part number - revision", what happens to assemblies when you modify the part and bump the revision code?
You need to use pack and go to rename the part to ensure that all assemblies (and drawings) get updated at the same time.
Thanks for the feedback, Bill!
I agree, the revision as part of the file name is not ideal, but I'm working with a vendor who has asked me to do it that way so I'm trying to accomodate. I usually "Save As" to change the file name, so the new version will be referenced by all assemblies but the old version still exists, to be tucked away in a "Previous Versions" folder.