Reported via James Smith:

About a month ago, I discovered an issue in TEM where a business object with children was being maintained on a maint doc. The business object itself and more importantly, the collection of children objects, all used synthetic keys based on a sequence as their PK’s, and on copy, I found we had to clear the PK’s manually in the processAfterCopy on the maintainable so that the PK’s were reassigned with the document saved them again; if we didn’t do the key clearing, then the children business objects were “stolen” by the object created by the copy and removed from the original. I talked to Doug Pace to see what KC did about this, and he saw two examples of this: one where they cleared the keys and one where they had forgotten (causing the “stealing” issue). Again: I’m not sure what help KRAD could provide to avoid this situation but it’s so easy to forget and cause problems that if there was a way to fix it, I think it would be very helpful for all of the client applications.

At this time, it looks like we are clearing the basic primary keys but do not have the code to clear all keys associated with the maintenance document, like those on collections or those on child objects. We should be doing this if preserveLockingKeysOnCopy is not set. Verify whether this is still a problem in KRAD and fix it if it is.