Features implemented both for OData V4 and OData V2 models in UI5: * Inline creation rows: Allow for a quick creation of new entries within a table without separate forms or popups. * Deep create: Allows to create one or more subentities for a navigation property of a newly created parent entity with a single OData request.

1. Inline creation rows, deep create
Patric Ksinsik, SAP SE
Uwe Reeder, SAP SE
July 6th, 2023

2. Agenda
Inline creation rows
Use case, APIs, coding, demo
Deep create
Use case, APIs, coding, demo

3. 3
Feature offered with identical APIs both for OData V4 and V2
Use case: Quick creation of entries in a table without separate “create button”
APIs
–Create new entry via ODataListBinding#create with “inactive“ parameter
▫ Inactive context  Not sent to server before first property update
▫ Use case “required properties for creation”:
App can cancel activation via createActivate event handler
–Get context status via Context#isTransient and Context#isInactive
Demo: Creation of sales orders and line items on RAP OData V2 service
▫ Feature demo
▫ Code demo with debugger
Docu on create: OData V4 and OData V2
Inline creation rows

4. 4
Feature offered with identical APIs both for OData V4 and V2
Use case: SAP backend interfaces for document creation typically offer deep
create
–Document and its line items is created with one service request
–Example: Sales order and sales order line items
Deep create triggered by ODataListBinding#create for a list binding with a
transient parent context
–One POST request to create document and line items within payload
–Bindings are updated from deep response
Deep create

5. 5
Demo: DeepCreate sample app in UI5 Demo Kit
Documentation
Deep create

6. Patric Ksinsik, Uwe Reeder
SAP SE
p.ksinsik@sap.com, uwe.reeder@sap.com