Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
There can be quite a few config options that affect this, I went through this with PTC support ~10 years ago. I made a config file called merge.pro that has every reference scope config option (they may have added some new ones since then):
allow_ref_scope_change YES
default_ext_ref_scope ALL
default_object_scope_setting ALL
default_object_invalid_refs COPY
ignore_all_ref_scope_settings YES
model_allow_ref_scope_change YES
scope_invalid_refs COPY
In Reply to David Haigh:
Found the problem thanks to a suggestion by Ron Grabau.
default_ext_ref_scope was set to None, setting it to All fixed the issue.
I need to make a mapkey to toggle this setting.
David Haigh