Make "Get Latest" propagate through

Make "Get Latest" propagate through

aleksei_ovsienko
Advocate Advocate
151 Views
2 Replies
Message 1 of 3

Make "Get Latest" propagate through

aleksei_ovsienko
Advocate
Advocate

I have noticed that a change made to a design only propagates to the design that consumes it directly. It does not go further automatically.

Example. 

I have an assembly made of 4 parts. Then a new model is derived from that assembly to be post-machined. Then a new model is derived from this post-machined weldment to be anodised. 


If I change one of the parts, I get a notification that I need to Get Latest in the first assembly that consumes them. But not in any of the derived ones. I have to open them all one by one, get latest and save, to make sure the change propagates to the next one. This is a rather weird workflow. It actually means a change can be made that is then not noticed by the final top level assembly.

It would be much preferable if there was some sort of a version manager available that would let me choose which models I want to push new information to when I save the part that I actually change. With default setting being push to all.

 

The other approach would be to keep all models loading from a local session until they are saved and checked into the cloud. This is how Creo does it. It gets rid of the need to constantly click Get Latest everywhere. You change something - everything else in session automatically pulls it. But the cloud only recieves it when you make choice to push to your cloud workspace (and from there to storage).

0 Likes
152 Views
2 Replies
Replies (2)
Message 2 of 3

TrippyLighting
Consultant
Consultant

I believe this is a current limitation that the Fusion team is aware of and will remove at some point.

I have re-posted this on the Autodesk Expert Elite Slack channel. With a little luck, someone from the Fusion Team will comment on this.


EESignature

0 Likes
Message 3 of 3

Pritam.patil
Autodesk
Autodesk

Thanks for reaching out.

As mentioned earlier, this is a current limitation in the product. However, improvements for this limitation are already in progress and are planned to be released to customers in the upcoming production release.

The workflow you mentioned is definitely one of the scenarios being addressed as part of this effort.

To help us validate the fix thoroughly, would you be comfortable sharing your dataset with us? This would allow us to verify that the issue is properly resolved with the ongoing project work and ensure the improvements behave correctly for your specific workflow.