I tend to agree with you, but historically, the 'protect' feature in Epic has been notoriously weak. Setting the protected element has always been an inverse operation (at least it seems that way to me).
I can, and would expect, that children in a protected element cannot be changed, but I should be able to modify or move the parent (unless the parent is also a child through nesting of the protected element) as long as I don't change content of the protected child.
It could be that Epic is not only reading the linage of the elements, but also the OIDs of the active document and thus not allowing the OID to be modified.
The last thing (and I had to go start up the Epic computer) is you may want to check the 'set protection' option (help 7999) and see if this may or may not help you out.
If it does, then you could run it through the XUI as needed.
---- James Sulak <firstname.lastname@example.org> wrote:
> Thanks, Clay. I did think of that, but I was hoping there was an
> easier, built-in solution. Especially considering that we already use
> some of those callbacks for other purposes.
> I'm a bit surprised that there's not an easier way to do it, since it
> would be a common requirement for customizations where you want to force
> the user to modify certain elements - like cross references - through a
> XUI interface. Oh well.