Question Re: Strange Behaviour in RAP Managed with Draft functionalty in Technology Q&A

Strange Behaviour in RAP Managed with Draft functionalty

abhishek_nag — Sun, 14 Jan 2024 03:02:26 GMT

I have developed RAP Managed application with Draft functionality. And in my BD, I have mandatory field check on a key field say 'OrderNo' during create and Read only during Update something like below.

field ( mandatory : create, readonly : update ) OrderNo;

Now when I try create, it doesnt take me to the create page. It gives mandatory field error even before navigating to create Page. The error is as follows

At create the mandatory element 'ORDERNO' of entity 'zc_ord1' was not provided

Now However this issue is not applicable for non-draft Application.

Q1> if this happens, this should happen both for draft and non-draft.

Q2> I have not written a single line for Validation. In fact there is no validation. Then where this message is coming from. Is this from standard framework. If yes then why I dont get message in a non-draft functionality if I miss mandatory field

Re: Strange Behaviour in RAP Managed with Draft functionalty

junwu — Sun, 14 Jan 2024 13:12:01 GMT

I guess there is no odata call for creation for nondraft when you click create button

Re: Strange Behaviour in RAP Managed with Draft functionalty

JessieCheah — Mon, 29 Jan 2024 09:07:54 GMT

Hi Abhishek,

I'm going to assume you are using oData V2.

At the moment Fiori Element does not support mandatory:create, as no popup box is appearing to enter the mandatory fields. With draft, there is indeed an oData call to the backend and the error message comes from there because no mandatory fields were sent from UI to create the draft entry.

Regards,
Jessie

Re: Strange Behaviour in RAP Managed with Draft functionalty

SachinArtani — Fri, 16 Feb 2024 04:37:18 GMT

Hi Jessie,