OData Connector for Informatica

In this article you will learn how to integrate OData data in Informatica without coding in just a few clicks (live / bi-directional connection to OData). OData Connector can be used to integrated any REST API which supports OData Standard. You can view tables, read data from tables using this connector. It also comes with some example OData Services to get started..

Using OData Connector you will be able to connect, read, and write data from within Informatica. Follow the steps below to see how we would accomplish that.

Download Documentation

The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc.

If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started.

Connect to OData in other apps

Connect to OData in SSIS

Connect to OData in SQL Server

Connect to OData in Power BI

Connect to OData in SSRS

Connect to OData in MS Access

Connect to OData in MS Excel

Connect to OData in SSAS

Connect to OData in C#

Connect to OData in Python

Connect to OData in JAVA

Connect to OData in Tableau

Connect to OData in SAP Crystal Reports

Connect to OData in Azure Data Factory (Pipeline)

Connect to OData in Azure Data Factory (SSIS)

Connect to OData in Talend Studio

Connect to OData in UiPath

Connect to OData in PowerShell

Connect to OData in ODBC

NOTE: If you need to consume API which is not listed on connector library page then please refer to the below article links. It talks about how to read / write pretty much any API and not just OData API. It explains various API tips / tricks using our other Universal Drivers not mentioned in this article (i.e. ZappySys JSON / XML and CSV Drivers).
How to read API data in Informatica (Call JSON / XML SOAP Service)
How to write data to API (POST) in Informatica (Call JSON / XML SOAP Service)

Introduction

JSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access OData data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate OData / XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read OData / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate OData or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica, Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

Download Install ZappySys ODBC PowerPack (API Driver for OData included)
Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

High level Steps for Import OData data using Informatica (Read OData API data)

Before we dive deep to learn how to load OData data in Informatica (i.e. OData to SQL Table), Here the summary of high-level steps you need to perform to import OData in Informatica (same steps for Import JSON / XML / REST API).

Download and Install ZappySys API Driver (for connecting to OData)
Create ODBC DSN using ZappySys API driver and choose OData Connector during Wizard
Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
Import OData Source Definition in the Informatica Mapping Designer > Sources Tab
Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
Create source to target mapping in Mappings tab
Save mapping (name m_API_to_SQL_Load )
Create Session using the mapping we created in the previous step
Save Workflow and execute to load OData data into SQL Table. Verify your data and log.
Loading OData data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read any API / JSON data in Informatica (Load OData to SQL Table)

Below video is not about OData API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Watch this video on YouTube

Getting Started – Import OData to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from OData and load data into SQL Server Table using Informatica Workflow.

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from OData using Informatica we first need to create a DSN (Data Source) which will access data from OData. We will later be able to read data using Informatica. Perform these steps:

Install ZappySys ODBC PowerPack.
Open ODBC Data Sources (x64):
Create a User Data Source (User DSN) based on ZappySys API Driver

ZappySys API Driver

You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.
When the Configuration window appears give your data source a name if you haven't done that already, then select "OData" from the list of Popular Connectors. If "OData" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

ODataDSN

OData

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

No Authentication [Http]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

No Authentication [Http]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
Optional Parameters
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...
IgnoreSSLCertificateErrors	Fill in the parameter...
SslVersion	Fill in the parameter...

Windows Authentication [Http]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

Windows Authentication [Http]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
Optional Parameters

Basic Authentication [Http]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

Basic Authentication [Http]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
UserName	Fill in the parameter...
Password	Fill in the parameter...
Optional Parameters
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...
IgnoreSSLCertificateErrors	Fill in the parameter...
SslVersion	Fill in the parameter...

NTLM Authentication [Http]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

NTLM Authentication [Http]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
UserName (i.e. Domain\UserName)	Fill in the parameter...
Password	Fill in the parameter...
Optional Parameters
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...
IgnoreSSLCertificateErrors	Fill in the parameter...
SslVersion	Fill in the parameter...

Token Authentication [Http]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

Token Authentication [Http]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
Token	Fill in the parameter...
Optional Parameters
AuthScheme	Fill in the parameter...
AuthHeader	Fill in the parameter...
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...
IgnoreSSLCertificateErrors	Fill in the parameter...
SslVersion	Fill in the parameter...

OAuth Connection for OData API [OAuth]

Fill in all required parameters and set optional parameters if needed:

ODataDSN

OData

OAuth Connection for OData API [OAuth]

https://services.odata.org/V3/Northwind/Northwind.svc

Required Parameters
Optional Parameters
GrantType	Fill in the parameter...
OAuthVersion	Fill in the parameter...
ClientId	Fill in the parameter...
ClientSecret	Fill in the parameter...
UserName	Fill in the parameter...
Password	Fill in the parameter...
Scope	Fill in the parameter...
AuthUrl	Fill in the parameter...
TokenUrl	Fill in the parameter...
ReturnUrl	Fill in the parameter...
ExtraAttributesForTokenRequest	Fill in the parameter...
ExtraAttributesForAuthRequest	Fill in the parameter...
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...
IgnoreSSLCertificateErrors	Fill in the parameter...
SslVersion	Fill in the parameter...

Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
Click OK to finish creating the data source.

Video instructions

Watch this video on YouTube

Create Connection in Informatica Workflow Designer

Once you create DSN using API Driver our next step is to define a connection for OData source in Informatica PowerCenter Workflow designer.

Open Workflow designer [W] icon
Goto Connections > Relational

Create a new connection for OData in Informatica
Click New and select ODBC

Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)
Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)

Configure OData connection in Informatica for REST API – Using ZappySys API Driver
Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import OData Source Definition in Informatica Mapping Designer

Now let’s look at steps to import OData table definition.

Open Informatica Mapping Designer (Click [D] icon)
Click on Source Icon to switch to Sources designer
From the top menu > Click on Sources > Import from Database …

Import OData Source definition in Informatica Mapping Designer (JSON file or REST API)
Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.

DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
—————————————————-
Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.

Select OData Source Table in Informatica Mapping Designer (JSON file or REST API)
Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
Optionally once table structure is imported you can rename it

Rename imported table definition in Informatica Source Designer
That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).

Now lets look at steps to import target table definition in Informatica mapping designer.

In the Mapping Designer, Click on Target Icon to switch to Target designer
From the top menu > Click on Targets > Import from Database …
Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).

Import target Table Definition in informatica
Enter your userid , password and Schema name and click Connect to see tables
Select Table name to and click OK import definition.

Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

First open Mapping Designer (Click [D] icon)
Drag JSON Source from sources folder
Drag SQL Table from Targets folder
Map desired columns from Source to target

Define Source to Target mapping for OData to SQL Table load in Informatica
For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
```
TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')

 --For ISO use below way
                TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')
```
Informatica OData to SQL Table Mapping – Datatype conversion (nstring to datetime)
Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

Open workflow designer by click [W] icon.
Launch new workflow creation wizard by click Workflow top menu > Wizard
name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)

Creating Informatica Workflow – Wizard UI (Import OData data to SQL Table)
Finish the wizard and double-click the Session to edit some default properties.
First change Error settings so we fail session on error (By default its always green)

Fail Informatica Session on error (OData data to SQL Load)
Select JSON connection for Source

Select OData Source Connection in Informatica – Load OData data to SQL Table
Change default Source query if needed. You can pass parameters to this query to make it dynamic.

Modify OData Source SQL query – Pass parameters, change URL, set filter etc
Select Target connection of SQL Target Table

Select SQL Target Connection in Informatica – Load OData data to SQL Table
Save workflow
That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Loading OData data to SQL Table in Informatica (Import REST API or JSON Files)

POST data to OData in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

Watch this video on YouTube

Keywords

Advanced topics

Create Custom Stored Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
Enter the desired Procedure name and click on OK:
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
```
CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';
```
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
```
Exec usp_get_orders '1996-01-01';
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

Go to Custom Objects Tab and Click on Add button and Select Add Table:
Enter the desired Table name and click on OK:
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
```
SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
```
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
```
SELECT * FROM "vt__usa_orders_only"
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Actions supported by OData Connector

OData Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

List Tables (JSON API)

[Read more...]

List Tables (XML API)

[Read more...]

Generic Read Data (JSON API)

[Read more...]

Parameter	Description
TableName	Read data from specified module (Json Format API)

Generic Read Data (XML API)

[Read more...]

Parameter	Description
TableName	Read data from specified module (Xml Format API)

Read [$parent.name$]

[Read more...]

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [Read more...]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body	Request Body content goes here
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

OData Connector Examples for Informatica Connection

This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.

Read all records from an JSON OData Service Table [Read more...]

SELECT * FROM Customers

Read all records from an XML OData Service Table [Read more...]

SELECT * FROM read_data_xml WITH(TableName='MyTable')

Filter records using server side criteria [Read more...]

SELECT * FROM Customers WITH( SearchCriteria='Country -eq ''USA'' ')

Filter records using client side criteria [Read more...]

SELECT * FROM Customers WHERE Country = 'USA'

List all Tables (JSON Based Format) [Read more...]

SELECT * FROM list_tables_json

List all Tables (XML Based Format) [Read more...]

SELECT * FROM list_tables_xml

Conclusion

In this article we discussed how to connect to OData in Informatica and integrate data without any coding. Click here to Download OData Connector for Informatica and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download OData Connector for Informatica Documentation

More integrations

Other application integration scenarios for OData

SSIS

SQL Server

Power BI

SSRS

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Other connectors for Informatica

Amazon Ads

Amazon MWS

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

DropBox

FastSpring

Google Drive

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

Nativo

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Download OData Connector for Informatica Documentation

Common Searches:

How to connect OData in Informatica?
How to get OData data in Informatica?
How to read OData data in Informatica?
How to load OData data in Informatica?
How to import OData data in Informatica?
How to pull OData data in Informatica?
How to push data to OData in Informatica?
How to write data to OData in Informatica?
How to POST data to OData in Informatica?
Call OData API in Informatica
Consume OData API in Informatica
OData Informatica Automate
OData Informatica Integration
Integration OData in Informatica
Consume real-time OData data in Informatica
Consume real-time OData API data in Informatica
OData ODBC Driver | ODBC Driver for OData | ODBC OData Driver | SSIS OData Source | SSIS OData Destination
Connect OData in Informatica
Load OData in Informatica
Load OData data in Informatica
Read OData data in Informatica
OData API Call in Informatica