In history-based software, if you make in-context relations between two parts in an assembly, those relationships always have to go one direction. You can't drive A with B and then drive B with A, that's called a circular reference. And we are taught to avoid that like the plague.
But sometimes in real design scenarios, that's how you get your information. You need CAD software that can hang with that sort of workflow. In Synchronous, the relations aren't stored (unless you tell them to be), so you can move that part up to this part and then this part up to that part.
Again, this is kind of old, but I think the concepts are still valid. Change a sheet metal part to match a solid, and then change the solid to match the sheet metal part. No warning bells, no best practice police, just real design intent flexibility.