RAP draft + facet two children deep

[ArneVH]

Hi,

We're creating an app using RAP managed scenario with draft and oData V4.
We're getting the following error when opening the object page of child 1:

I have a root node -> child 1 -> child 2 -> child 3. All objects can be created in draft, and saved together.

Our child 2 is an object we want to hide from the end-user, it has a 1-to-1 relation with child 1 and requires no input to create (in the current variant).

To achieve this we added a determination on child 1 which creates child 2 behind the scenes upon create of child 1. => This is working fine, although potentially not a best-practice??? Open to suggestions...

Our CDS-view of child 1 then contains an @UI.facet annotation where the 'targetElement' = _Child2._Child3

=> This seems to be the cause of our above mentioned error, but we cannot figure out what exactly is the problem.. all objects are draft enabled and the draft table of our _ExtraWork (child 3) object does indeed have this field 'IsActiveEntity'.

Moving our facet from child 1 to child 2 solves this, so the underlying object seems to be configured correctly.

Similarly, remove the draft enablement and the facet is displaying correctly.

Is it simply a limitation of the framework that we cannot use associations in our facet and draft enabled objects??

Other creative solutions are also always welcome - we're actively trying to push the limits of what is possible without custom UI development 🙂

The reason we cannot simply merge child 1 and child 2 is because we have a variant of the hierarchy where the child 1 to child 2 relation becomes a 1-to-many and we do in fact want to make it visible to the end-user...

Thanks for any input!
Arne

[ArneVH]

Some extra info:
- I got it working by defining the cardinality 'to one' between child 1 and child 2.

Ideally we don't need to do this because then we'll have to split our other variant on cds-level with the same association with a 'to many'...