Retrieve OData
Infoveave Data Automation — RESTful
$filter, $skip, $top — OData's power, directly inside your workflow.
OData (Open Data Protocol) is the standardized query API used by Microsoft services, SAP, Business Central, and hundreds of ERP and enterprise systems. Retrieve OData connects to any OData v4 endpoint and retrieves filtered, paginated data using the native OData query syntax ($filter, $skip, $top) — without writing HTTP request code or parsing response envelopes manually. The result is a structured table that flows directly into the next workflow step, making Retrieve OData the right integration choice for any enterprise system that exposes an OData endpoint.
What Retrieve OData does
Connect to any OData-compliant service and retrieve structured data using standard OData filter, skip, and top parameters inside your Infoveave workflow. Supports ERP systems, Microsoft services, and any OData v4 endpoint.
When to use Retrieve OData
- Your source system exposes an OData v4 endpoint — such as Microsoft Business Central, SAP, Dynamics 365, or SharePoint
- You need to filter OData entities using standard OData filter expressions before retrieving data
- You need to paginate through large entity sets using $skip and $top parameters
- You want built-in retry handling for OData endpoints that occasionally return transient errors
When to avoid it
- You are connecting specifically to Microsoft Dynamics CRM — use Microsoft Dynamics, which provides native entity mapping and field support
- You are calling a non-OData REST API — use Execute API
- You are querying a GraphQL endpoint — use Execute GraphQL
- You are running a SQL query on a relational database — use Execute Query
Where it fits in your Infoveave automation
Retrieve OData is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Retrieve OData
Real scenarios where this transformation saves hours of manual work.
Business Central Purchase Order Retrieval
A procurement workflow retrieves open purchase orders from Microsoft Business Central via the OData API. The filter expression 'Status eq Open and OrderDate ge 2026-04-01' returns only current-month open orders. Results flow into a transformation pipeline that calculates expected delivery dates and generates a procurement summary dashboard.
SAP General Ledger Extract
A month-end workflow calls the SAP OData API to retrieve general ledger entries for the current period using $filter for posting date range and $top for batch size. Multiple workflow runs with $skip pagination retrieve all entries. Loaded into the financial reporting database via Insert into Database.
Inventory Position Sync
A daily inventory workflow calls the warehouse management system's OData API to retrieve current stock positions across all locations. $filter limits results to items below safety stock threshold. Retrieve OData retries up to 3 times on transient failures, ensuring the workflow completes reliably even when the WMS API is temporarily slow.
See Retrieve OData in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
business-central-odatapurchaseOrders/api/v2.0/companies(company-guid)3Status eq 'Open' and OrderDate ge 2026-04-010500Input Data
| (OData connection and resource configuration — no row input required) |
Output Data
| OrderID | VendorName | OrderDate | Status | TotalAmount |
|---|---|---|---|---|
| PO-2026-001 | Acme Supplies | 2026-04-02 | Open | 12500.00 |
| PO-2026-002 | Global Parts Ltd | 2026-04-05 | Open | 8750.00 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered OData service connection in Infoveave Studio. Includes the base URL and authentication (OAuth, API key, or Basic auth) for the OData endpoint.
Resource Name
The OData entity set name to query — such as 'purchaseOrders', 'salesOrders', 'items', or 'customers'. Corresponds to the entity set name defined in the OData service metadata.
Service Path
Optional path segment appended between the base URL and the resource name. Used for OData services where entity sets are nested under company GUIDs or API versions — for example '/api/v2.0/companies(guid)'.
Number of Retries
Number of times the activity retries the OData request if a transient error (network timeout, HTTP 429, HTTP 503) is received. Default is 3. Useful for OData services with rate limiting or occasional availability issues.
Filters
OData $filter expression that restricts the returned records. Supports all standard OData filter operators: eq, ne, gt, lt, ge, le, and, or, in, and string functions like startswith and endswith. Examples: 'Status eq Open', 'OrderDate ge 2026-04-01 and Status ne Cancelled'.
Skip / Top
OData pagination parameters. Skip sets the number of records to skip (offset). Top sets the maximum number of records to return per request. Use in combination with multiple workflow runs or looping activities to paginate through large entity sets.
Frequently asked questions
Everything you need to know about Retrieve OData in Infoveave.
Also in RESTful — and what runs before & after
Transformations in the same family as Retrieve OData, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Retrieve OData is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
