Editing wrong version of the file after Edit In Place

[ltomuta]

Every now and then I do some work on a file. Then I inset that file in an assembly while keeping it open. And Fusion does not mind.

Then because in the assembly I can't control the visibility of elements from the linked component (why?) I end up having to "edit in place" the component to toggle sketches/components visibility on/off.

Now I save the file and all looks good. But my file is still opened, with wrong version. And of course I return to it and make edits which are now in the wrong branch of the file history. And Fusion does little to stop me until I try to save the changes.

You may blame me for bad working style and not keeping track of that little version warning tringle but ... Shouldn't Fusion do more to help me keep it tidy? Like maybe not let me do EIP if the file is already open?

[kgrunawalt]

First, we understand the frustration of not being able to control visibility of inserted part (xref) elements other than components from the parent. You mention components but they can be hidden from the parent without editing the xref. Stay tuned.

It sounds like you have a handle on what is going on but would like more feedback and guard-rails. We have internal debates about how much we should block and how loudly we should warn in situations like this. Your post helps us get an idea of where we could improve in that respect. We could block opening B when also editing B in place, and vice versa. Or we could be louder about it when you edit something that cannot be saved because it is not the latest version.

In fact, we have made changes in the latest release to help when multiple people are working on the same assembly. Perhaps we need to do more when just one person is editing the same model twice.

I'm on the technical side of things but I'll relay this to our experience designer.

[tyler_henderson]

Regarding the need to control visibility of objects in inserted components,  as Katrin mentioned, we completely understand and we are currently working on that.

Regarding editing a Design in two places at the same time,

I feel like it's a bit too restrictive to disable EIP if a Design is also open in its own tab.  I know many users like to keep a Design open while they do edits to that Design in the context of an assembly, then jump to the open Design tab to update and view the changes outside of the assembly, or vice versa.

This is really a more general issue of being able to edit a non-latest version of a Design.  EIP does make this more probable for a single user, but it can easily happen in a team environment if two people have the same Design open.

Would it be sufficient to just pop up a warning anytime someone starts editing a non-latest version of a Design? 

[ltomuta]

A more visible warning could help. Making the opened tab read-only until latest version is loaded in it could also work (form me). A way to resolve the conflicting versions (diff and merge type thing?) would be awesome. 

As I mentioned in this other thread even once I knew that I had a problem I was not able to fix it and save my work with what appeared to be a easy and safe solution. So maybe the "Saving 0 of 1" dialog should hint to a better/proven way to solve the conflict other than just discard the recent work...

[ltomuta]

As for teams maybe the more likely conflict could be between Design and Manufacturing teams and thus I would see those two areas decoupled and versioned independently. My EIP may trigger some minor Design changes but that should not prevent me from saving my CAM work even if still dependent on an older version of the model.

[tyler_henderson]

---

@ltomuta wrote:

A more visible warning could help. Making the opened tab read-only until latest version is loaded in it could also work (form me). A way to resolve the conflicting versions (diff and merge type thing?) would be awesome. 

As I mentioned in this other thread even once I knew that I had a problem I was not able to fix it and save my work with what appeared to be a easy and safe solution. So maybe the "Saving 0 of 1" dialog should hint to a better/proven way to solve the conflict other than just discard the recent work...

---

Regarding the "Saving 0 of 1", did it only suggest discarding your work?  You should have seen this tooltip:

[tyler_henderson]

Sorry, the image attachment doesn't seem to be working.