An OData resource is a connection to a data store that adheres to the OData protocol. It is not so important to understand OData in detail; therefore, we will cover the most important points to know when connecting from SAP Build Apps.

An OData service defines a set of entities. These entities represent real-world things like customers, products, locations, and employees. Since OData services must provide metadata about the service, once you provide the URL to the service, SAP Build Apps will know what entities there are, their fields, and data types.
Each entity will define a set of fields, where each field represents a piece of information about that entity. For example, for customers, you might have the following fields:
- CustomerID
- CompanyName
- ContactName
- ContactTitle
- Address
- City
- Region
- PostalCode
- Country
- Phone
- Fax
So far, we have defined the nature of the data we want to store. However, eventually, we will store actual data in our OData service entity, and that data is represented as a set of rows, with each row having a value for each of the fields. So, we might have the following data:
More information about OData including the mock system with the Northwind example to test the usage can be found here: https://www.odata.org/
Example Data
CustomerID | CompanyName | ContactName | ContactTitle | Address |
---|---|---|---|---|
ALFKI | Alfreds Futterkiste | Maria Anders | Sales Representative | Obere Str. 57 |
ANATR | Ana Trujillo Emparedados y helados | Ana Trujillo | Owner | Avda. de la Constituci\u00f3n 2222 |