topic Re: Warning: This design contains Removed components which did not update. in Fusion Design, Validate & Document Forum

Warning: This design contains Removed components which did not update.

mah6786 — Mon, 04 May 2020 22:30:50 GMT

Hi,

I'm having some trouble understanding this warning. My sub-assembly isn't showing anything out of date, but the top-level assembly I'm trying to update does. Sure, it went away after I rolled back before any removes, saved, updated, rolled forward to the end, then updated again, but this whole operation seems very odd, since nothing changed in the sub-assembly.

In what situation is it useful to have the top level not update the removed component? Can this warning be safely ignored?

Re: Warning: This design contains Removed components which did not update.

jeff_strater — Mon, 04 May 2020 23:02:11 GMT

this is a valid question. I think that the logic here is: The Get All Latest command only iterates over the current existing set of components and updates them. Whether this is for efficiency, or what, I've lost track of. Perhaps the issue is that updating the Removed components would have to involve an automated version of what you do manually - roll back the design to the point where the component existed, update, then roll forward. That could be a costly operation, if there are many such components. I cannot think of a scenario offhand where updating a removed component could cause problems, but I suppose one is possible.

Whether this can be safely ignored is design-specific. Imagine you had a situation where you inserted a component, used that to Combine/Cut another component, then removed it. Then, later, that inserted component is scaled by 25%. If you don't update to the scaled version, that cut could be "wrong", in that it does not allow for the new size. But, certainly in a lot/most cases, this warning is innocuous and can be ignored.

Re: Warning: This design contains Removed components which did not update.

etfrench — Mon, 04 May 2020 23:47:17 GMT

How do you determine which removed component needs to be updated when there are multiple removed components scattered about in the project?

Re: Warning: This design contains Removed components which did not update.

mah6786 — Mon, 04 May 2020 23:48:05 GMT

Thanks for the replay. I do hope that the F360 team will find a way to streamline updating assemblies (deep updates, removed components, etc). The current implementation has a lot of room for improvement.

Re: Warning: This design contains Removed components which did not update.

jeff_strater — Tue, 05 May 2020 00:24:36 GMT

By "deep update", do you mean the ability to update from the top level, and not having to go bottom up through sub-assemblies? Or are you referring to something else? That definition of "deep update" is supported today. The one exception is Derive. Derive, today, unfortunately, does not participate in deep update.

Re: Warning: This design contains Removed components which did not update.

mah6786 — Tue, 05 May 2020 01:51:41 GMT

@jeff_strater I just tested deep update , and it does indeed work. For some reason I thought it didn't when I last tried it and have been propagating my updates manually this whole time. Thanks!

@etfrench I rolled to the beginning, not sure if works in all the cases. I still think it's a strange behavior. I don't think I ever had to do this in OnShape.

Re: Warning: This design contains Removed components which did not update.

motorhobo — Tue, 24 Aug 2021 16:12:02 GMT

@jeff_strater'But, certainly in a lot/most cases, this warning is innocuous and can be ignored.'

It really can't be ignored because the condition that invokes it propagates throughout every design in which the condition appears every time you use Remove. It then snowballs, so pretty soon you have a lot of un-updated, Removed components, and then if you DO actually have a problem like the one you mentioned above, you won't be able to identify which one actually caused the problem. People need to keep their designs clean and free of warnings and possible error conditions. It's not reasonable to advise people to just ignore a warning. Either the condition that throws the warning is problematic or it's not. If it is, then it's on the developers to solve the problem. If it's not, then there should be no warning.

This behavior is so insidious that I've stopped including components in other components for reference. Instead, I calculate absolute coordinates in 3D space and use those for subcomponent positioning. It's much more work and should be unnecessary, but since Remove slaps a big Warning icon on every parent component whenever a subcomponent changes, there's really no alternative. IMO Remove is much more hassle than it's worth, and until there' s a more intelligent way to handle referenced subcomponents, I'd advise users to avoid it.