Hi Matan,
Again a big thanks for your response! I followed your suggestion and re-checked the BOPF model. I also played around with the resolve by source / target node parameter and my association class. When setting them in the non-logical way, the data is not even displayed, so I'm quite convinced those settings are correct.
Unfortunatelly I still get the error during creation where the source key is the (wrong) key from node A and the node key the correct key from node B:
With error message "While execution, a meta data request of a certain node was caused in class"/BOBF/CL_CONFRT_COMPLETE". This request fails, because the node doesn't exist in the business object"A" and its used configuration object. But a node named "ROOT" with the requested key <GUID> instead exists in business object "B".
I based the wire scheme on the demo sales order, where a dummy form links the composite association of bo A (subnode "PARTY", the collection of bo B objects) to the list GUIBB of bo B objects via the cross-bo association of each bo B in the collection.
So this wire scheme works for display, but causes an error for creation (which seems quite justified thinking back to the wire scheme..).
Could you maybe give a few suggestions for those other UI design options, which would solve this problem? I noticed the create item of the sales order demo works, but there only a new entry is created in the composite association, linking an existing product (bo B). In my case bo B needs to be created and linked..
Many thanks!
Kind regards,
Bjorn