An OData service can be created in apps that have reporting enabled (e.g. Scrum). The OData service contains the definition of the object classes and properties that are exposed via the OData API.
Depending on where you create the OData service, various source objects can be used. For example, in order to gain access to your contracts, create an OData service inside your Contract Manager app.
Having created an OData service, you receive a URL which can then be used to access the data via a client like Microsoft Power BI. The OData protocol is a standardized protocol which is understood by any client - even a web browser.
Aside from the OData URL, you require the “Access for Applications” password for authentication.
Once reporting has been enabled in the app of your choice, you need to create the OData service in the context where your data is stored so that it can be queried.
To create an OData service, proceed as follows:
You need a password for applications to access your OData service. Create a password by opening the account menu (your user name) and clicking “Advanced Settings” > “Access for Applications”. Create a password valid for “Open Data Protocol (OData)”.
OData licenses are available in 10M and 100M versions.
OData volume licenses are checked when
The overview does not lower the number of available objects but the overview is not shown if there is no amount of any OData volume left.
When retrieving rows for a certain entity the OData volume is lowered by the number of rows retrieved. That means you are charged exactly by the number of rows retrieved no matter which filters are applied and how many data rows there are in original.