Hi all,
Was wondering if anyone knows the best-practice way to implement instance authorization on create in the RAP-framework?The documentation explicitly mentions create is not provided as there is no instance at create (yet). However there are s...
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 ...
Hi,We are building an application using the RAP-framework using managed functionality and with draft enabled.
We have a root with two children (project contract + top meetstaat). Please refer to screenshot below.
Top meetstaat has an input that r...
Hi Renzo,Upon further testing with the above mentioned solution I stumbled upon the problem that instance authorization on create for a child-node 2 deep is not possible?We have: project (root) -> project customer -> project customer contact personBo...
Hi,It seems I had a similar problem, however I got an explicit error message.I had some extra context with RAP + draft around my issue however... I fixed it by defining the _detail (first one) association as a 'one to one'. Then the facet can render...
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'...
