2 Replies Latest reply on Jul 13, 2018 10:18 AM by Josh Brady

Why is file flagged as modified when I make a different configuration active?

Dwight Livingston Jul 13, 2018 9:30 AM

Working with an assembly, I find if I make a different configuration active in a component, SW tags the component file as modified. This causes minor aggregations for our PLM. The component's file content hasn't changed, so I'd prefer that SW would recognize that everything is cool and not change the file status. Anyone know a setting for this?

Thanks

Dwight

Re: Why is file flagged as modified when I make a different configuration active?

David Sloop Jul 13, 2018 9:54 AM (in response to Dwight Livingston)

Solidworks bumps the revision often just from us opening the file on a newer service pack, or even on a different computer.
It also does it if we make a pdf file, or print and change the print settings...
We pretty much just ignore the -01, etc. minor revisions...
Like Show 0 Likes(0)

Actions
Re: Why is file flagged as modified when I make a different configuration active?

Josh Brady Jul 13, 2018 10:18 AM (in response to Dwight Livingston)

Just spitballin' here... Sorry, don't use PLM. Can you set SW to automatically open referenced files as read-only? This may be a nuisance if you're working in an assembly and modifying lots of its components, but if you're really just changing the assembly (switching referenced configs etc) then this might work.

If you are switching the component to some previously un-built config (such as a fastener or something that has loads of configs generated by a design table that have never been activated) then your opening times for the assembly may increase since the read-only part will have to be rebuilt in the new config every time you open the assembly.
Like Show 1 Likes(1)

Actions

Go to original post