Why does using SAVE AS dirty the originating file? See graphic below, original file 35483-02100 is okay. But after I open that assy and do a SAVE AS the originating file is dirtied in the parent assy (see 2nd graphic). Is this a bug? Should this be fixed? I know there are other methods (Vault Copy Design and such) but to make a simple new assy with a change or 2 SAVE AS should suffice. Comments appreciated.
When using the Vault, utilizing 'save as' is not recommended. A better solution would be to use 'copy design' from within the Vault.
Yep, I get that by the fact that it dirties the file. But it is a valid method of saving a copy. Thanks.
Hi Mikel. Not sure about this when working outside of Vault. The below is copied from an email I received from our support supplier.
"The dirty subassembly only appears while having the main assembly open. When closing the main assembly, I am prompted to save. If I say no and re-open the assembly, subassembly doesn't appear dirty anymore. I have seen this in the past quite a few times and have always resolved by using this method. Not sure if a bug but would be a great enhancement if commands such as Save As would not dirty the original file as it confuses users and adds additional steps (close, don't save, reopen, etc) to the workflow."
I understand the other posters opinion (jclaidler) but think that this 'apparently' dirtied file bug should be fixed. The unknowing user would check the file out and in which is clearly un-needed. Using Save As is just a quick and simple method of creating a new assy (or part as this bug also dirties part files) so that I can swap out 1 piece of the assy with another. Copy Design is great although sometimes laboursome and I think is an overkill for creating new versions of small assemblies.
We used to experience this all of the time. I now use the "Save and Replace component" command buried in the Assemble/Productivity menu. Using this, I've stopped dirtying files, and can save a little time too as it goes right to naming the file, replaces it in the assembly immediately. I can then open it for editing.
Ground and root, rename browser node, DOF analysis, and Alpha Sort components are also useful tools buried here.
Thanks Sam. I use a few of those ribbom commands but not Save And Replace. I'll give it a go. Still, I woul like the apparent bug to be fixed. Have to log it on the wishlist
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!