Replace component doesn't keep constraints made to the origin.

[andrewdroth]

I'm replacing parts in an assembly with phantom assemblies of the same name. I was surprised when I used the Replace Component option that it couldn't retain the flush constraints to the origin work planes. 

For example, each part has it's YZ, XZ, and XY planes constrained flush to the matching ones in the assembly.

Since those planes are universal between parts and assemblies I don't see why it would get tripped up by that?

[James_Willo]

Hi Andrew, I can reproduce this, I will ask the team about this, it might be that it's as designed since an assembly is different from a part, but I totally get what you're saying. 

[James_Willo]

The reason this works with parts and not with part to assembly is because the browser structure IDs are different.

Part origins have one set of Browser Node internal IDs applied to them, but in assemblies, the part origins have a different Node ID so the constraint fails. If you replace a part with a part, the origin Node IDs match and the constraint will be solved. 

Please post this idea in the Idea Station if you would like it to be considered for future development. We're not sure how easy this feature is to implement though as we haven't looked into how it would work with migrated data.