You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development/specific/odata.md
+45-49Lines changed: 45 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,67 +5,39 @@ By default, you can bind all public attributes of your implementation class to U
5
5
### Define Second Model
6
6
As an example, we will use the test OData service `/sap/opu/odata/DMO/API_TRAVEL_U_V2/`, which is available in most ABAP systems. Ensure the service is publicly accessible. Use the following method to define the model and make it available under the name `TRAVEL`:
7
7
```abap
8
-
client->follow_up_action( client->_event_client(
9
-
val = z2ui5_if_client=>cs_event-set_odata_model
10
-
t_arg = value #(
11
-
( `/sap/opu/odata/DMO/API_TRAVEL_U_V2/` )
12
-
( `TRAVEL` ) ) ) ).
8
+
client->follow_up_action( client->_event_client(
9
+
val = z2ui5_if_client=>cs_event-set_odata_model
10
+
t_arg = value #(
11
+
( `/sap/opu/odata/DMO/API_TRAVEL_U_V2/` )
12
+
( `TRAVEL` ) ) ) ).
13
13
```
14
14
### Bind Data
15
15
Next, bind this OData model to your view definition. Since we’re using a non-default model, we must explicitly specify the model name for each binding. Here's an example:
0 commit comments