2024 Jun 10 1:54 PM - edited 2024 Jun 11 7:10 AM
Hi Everyone,
I have a RAP OData service with multiple entities with navigation relation( composition ).
UI developer can be able to do DEEP CREATE with multiple entities in a single call?
but for Update operations which may include update, create, and delete we need to use Batch operation to club all operations and send in a single request to the backend.
But I want to use change_set( deferred mode ) operation for all the create, update and delete operations so that it will happen in one session with either complete success of all operations or None in case of any error in any of the operation.
I saw the invocation grouping UI annotation for grouping actions in a change_set.
But how to acheive same for create, update and delete operations( CRUD ).?
Thank you in advance.
Request clarification before answering.
In RAP, multiple operations must be grouped under a single changeset within the $batch call to ensure they are processed as one atomic Logical Unit of Work(All-or-nothing). Because the RAP runtime handles the DB commits automatically, there is no need to explicitly implement defer mode or redefine changeset methods as you would in a classic DPC_EXT class.
The Create, Update, and Delete methods of the RAP Business Object are designed for mass processing, meaning their IMPORTING parameters(keys or entities) contain multiple entries representing all the operations bundled within that single changeset.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may try to use concept #ISOLATION and #CHANGE_SET
Using #ISOLATION - You may allow process multiple data which are valid per your use case and show failed records as error...
You may want to watch below reference videos, may help:
Hope this helps...
Thanks-
Abhishek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@AbhishekSharma, But I need this with create operation, change operation, and delete operation of the entities, not to specific action of the Business Object.
| User | Count |
|---|---|
| 11 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.