Francisco, Thanks for including my issue in your post! Perhaps we can discover something beneficial between us.
I am running version 9.14_05 still but was considering an upgrade due to this issue as well as the recent end-of-support notification on my version. But it seems that between our 2 versions, we are getting the exact same issue.
Setting the COPY parm to 'N' also works for me, however, that is an issue since I need some of the target CR fields to be pre-populated. I will see if I cannot simply specify the values for those particular fields in the copy command...
select "<hidden token value>", "<visible token value>" from dual
If in a workflow step, I would use:
ksc_store DESCRIPTION="<token value>"
The problem is that I am struggling with how to get that parent reference... Since both parent and child have the other as a referenced Request, shouldnt I be able to reference that value via a token? Or do I have to find out where they are linked in the database and then work from there?
Surely, I am not the first to do these things, but I am certainly no expert either!
If you are creating the request with references in the UI rules you can take your request id use it against knta_references to obtain the parent id project save it on a field and after that you can recover the data using that id with a select to the request, request headers and request details and set it to the fields.