Retrieving Data via OData

With the help of OData, data from Avendoo can be exchanged with other applications. This involves raw data, which is always global and must be interpreted and transformed independently. Raw data from various systems can be used to build a data warehouse that centrally collects information from Avendoo and other applications in one location. The data warehouse enables the analysis of the data in order to make informed decisions or to identify trends and patterns.

1

Define use cases for which you want to use OData.

2

Check whether the use cases can be implemented more efficiently with Avendoo reports.

If your use case cannot be mapped with the help of reports, coordinate the implementation of the use case with your Avendoo contact person.

FAQ – Frequently asked questions about OData in Avendoo

In what form is the raw data delivered?

An OData table with raw data is represented as a JSON or XML structure that represents an entity collection, where each row is a data record (e.g. a person, a product) and each column is a property,
as shown in the example of a “Person” entity with fields such as PersonId, FirstName, LastName, Email – typically retrievable via an HTTP GET request to an OData endpoint.

What should be considered when making OData queries?

OData queries should be designed to load only new or changed data records. If all data records are queried again with each call, an unnecessarily large number of API requests are generated, the system is burdened
and the purchased retrieval quota is quickly used up.

You can avoid unnecessary API load by filtering changes (timestamps) or – if available – using delta queries – e.g.: “/Products?$deltatoken=abc123”. Both methods ensure that only new or changed data records are retrieved instead of loading everything each time.

How many OData API calls do I need per day?

There is no fixed number of OData API calls per day – the need depends entirely on how often your system retrieves data, how many data records you load and how efficiently your queries are designed. Your usage therefore depends entirely on your individual needs. See what you need and use requests efficiently.

Important factors

How often synchronization occurs (every X minutes or once daily/nightly)
How many tables/entities are queried
Whether full queries or only changes are loaded
How many data records are returned per query
Whether programs have API limits (e.g. SAP, SharePoint etc.)

What are the concerns of works councils or other internal parties?

Works councils do not look at the technology itself in technical solutions such as OData, but at the effects on employees. Concerns cannot be “configured away”, but can be greatly mitigated through clear rules, transparency and protective measures.

Possible measures

Define earmarking in writing and no hidden evaluations
Technically enforce data minimization and minimize retrievals
Document data flows: Which systems access in which cycle and what does the concrete data flow look like?
Access restrictions and pseudonymization, if possible
No performance or behavior monitoring

Prerequisite

Avendoo license to use the OData interface
Author account with the permission to use Odata API
Experience with databases, interfaces, and Avendoo

How can we help you?

Search here or have a look at the topics below

Retrieving Data via OData

FAQ – Frequently asked questions about OData in Avendoo

Was this article helpful?