Design time
The first step in the creation of any OData service is a good design. The better the service is modeled before the initial draft, the less complicated the coding will be. What is important to remember during the design phase is that each and every piece of information has to be uniquely identified with the key, and nested structures inherit the key of the parent, simultaneously adding their own. This will be demonstrated in the following examples.
The ZODATA_SERVICE service, which is used in the sample SAPUI5 application, needs to have at least one collection (entity set) available at /FlightsSet. Additionally, it has to be filterable with the DepartureAirport property, and the following properties should be provided for display ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access