Salesforce Connector for Informatica Salesforce Connector can be used to extract/load large amount of data from/in Salesforce.com without any programming. You can use simple Table mode or Query mode with full SOQL query language support (SOQL=Salesforce.com Object Query Language). In this article you will learn how to quickly and efficiently integrate Salesforce data in Informatica without coding. We will use high-performance Salesforce Connector to easily connect to Salesforce and then access the data inside Informatica. Let's follow the steps below to see how we can accomplish that! Download Documentation Salesforce Connector for Informatica is based on ZappySys Salesforce Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few.

Connect to Salesforce in other apps Connect to Salesforce in SSIS Connect to Salesforce in SQL Server Connect to Salesforce in Power BI Connect to Salesforce in SSRS Connect to Salesforce in MS Access Connect to Salesforce in MS Excel Connect to Salesforce in SSAS Connect to Salesforce in C# Connect to Salesforce in Python Connect to Salesforce in JAVA Connect to Salesforce in Tableau Connect to Salesforce in SAP Crystal Reports Connect to Salesforce in Azure Data Factory (Pipeline) Connect to Salesforce in Azure Data Factory (SSIS) Connect to Salesforce in Talend Studio Connect to Salesforce in UiPath Connect to Salesforce in PowerShell Connect to Salesforce in ODBC

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 Salesforce 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 Salesforce / 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 Salesforce / 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  Salesforce 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.

1. Download Install ZappySys ODBC PowerPack (API Driver for Salesforce included)
2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
3. 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 Salesforce data using Informatica (Read Salesforce API data)

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

1. Download and Install ZappySys API Driver (for connecting to Salesforce)
2. Create ODBC DSN using ZappySys API driver and choose Salesforce Connector during Wizard
3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
4. Import Salesforce Source Definition in the Informatica Mapping Designer > Sources Tab
5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
6. Create source to target mapping in Mappings tab
7. Save mapping (name m_API_to_SQL_Load )
8. Create Session using the mapping we created in the previous step
9. Save Workflow and execute to load Salesforce data into SQL Table. Verify your data and log.
   

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

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

Getting Started – Import Salesforce to SQL Server in Informatica

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

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

Step-by-step instructions

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

1. Download and install ODBC PowerPack.

2. Open ODBC Data Sources (x64):

   

3. Create a User data source (User DSN) based on ZappySys Salesforce Driver

   ZappySys Salesforce Driver

   
   • Create and use User DSN if the client application is run under a User Account. This is an ideal option in design-time, when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit.
   • Create and use System DSN if the client application is launched under a System Account, e.g. as a Windows Service. Usually, this is an ideal option to use in a production environment. Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.

4. Now, we need SalesForce Connection. Lets create it.

5. Now, When you see DSN Config Editor with zappysys logo first thing you need to do is change default DSN Name at the top and Click on Preview Tab, Select Table from Tables Dropdown or you can enter or modify a SOQL query and click on Preview Data.
   This example shows how to write simple SOQL query (Salesforce Object Query Language). It uses WHERE clause. For more SOQL Queries click here.
   SOQL is similar to database SQL query language but much simpler and many features you use in database query may not be supported in SOQL (Such as JOIN clause not supported). But you can use following Queries for Insert, Update, Delete and Upsert(Update or Insert record if not found).

   SELECT * FROM Account WHERE Name like '%Oil%'
   

6. Click OK to finish creating the data source

Video Tutorial

Create Connection in Informatica Workflow Designer

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

1. Open Workflow designer [W] icon
2. Goto Connections > Relational
   

   Create a new connection for Salesforce in Informatica

3. Click New and select ODBC
   

   Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)

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

   Configure Salesforce connection in Informatica for REST API – Using ZappySys API Driver

6. 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 Salesforce Source Definition in Informatica Mapping Designer

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

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

   Import Salesforce Source definition in Informatica Mapping Designer (JSON file or REST API)

4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
5. 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 Salesforce Source Table in Informatica Mapping Designer (JSON file or REST API)

6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
7. Optionally once table structure is imported you can rename it
   

   Rename imported table definition in Informatica Source Designer

8. 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.

1. In the Mapping Designer, Click on Target Icon to switch to Target designer
2. From the top menu > Click on Targets > Import from Database …
3. 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

4. Enter your userid , password and Schema name and click Connect to see tables
5. 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.

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

   Define Source to Target mapping for Salesforce to SQL Table load in Informatica

5. 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 Salesforce to SQL Table Mapping – Datatype conversion (nstring to datetime)

6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
7. 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.

1. Open workflow designer by click [W] icon.
2. 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 Salesforce data to SQL Table)

3. Finish the wizard and double-click the Session to edit some default properties.
4. First change Error settings so we fail session on error (By default its always green)
   

   Fail Informatica Session on error (Salesforce data to SQL Load)

5. Select JSON connection for Source
   

   Select Salesforce Source Connection in Informatica – Load Salesforce data to SQL Table

6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
   

   Modify Salesforce Source SQL query – Pass parameters, change URL, set filter etc

7. Select Target connection of SQL Target Table
   

   Select SQL Target Connection in Informatica – Load Salesforce data to SQL Table

8. Save workflow
9. 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 Salesforce data to SQL Table in Informatica (Import REST API or JSON Files)

POST data to Salesforce 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

Keywords

how to import Salesforce in informatica | how to read Salesforce data in informatica powercenter | how to test json from informatica | how to use Salesforce data as source in informatica power center | how to connect Salesforce in informatica 10 | informatica how to import data from Salesforce | informatica jtx to import Salesforce (use of java transformation) | informatica plugin for restful api using json | informatica power center and Salesforce support | informatica read Salesforce | informatica rest api | informatica Salesforce connector | json parser import informatica

Query Examples

This guide provides examples for using the ZappySys Salesforce ODBC Driver to perform bulk API operations and DML (Data Manipulation Language) actions on Salesforce. You’ll learn how to leverage the Bulk API to insert, update, upsert, and delete large datasets from external sources such as MSSQL, CSV, Oracle, and other ODBC-compatible systems. By using external IDs and lookup fields, you can easily map data from your source systems to Salesforce. These examples will help you execute high-performance operations efficiently using EnableBulkMode, EXTERNAL options, and more.

Bulk Mode - Insert Large Volume of Data from External Source (e.g., MSSQL) into Salesforce

INSERT INTO Account
SOURCE (
    'MSSQL',
    'Data Source=localhost;Initial Catalog=tempdb;Integrated Security=true',
    'SELECT TOP 1000000 
         C_NAME AS Name,
         C_CITY AS BillingCity,
         C_LOC AS NumberofLocations__c  
     FROM very_large_staging_table'
)
WITH (
    Output = 1,
    EnableBulkMode = 1
)

-- Notes:
-- 'MSSQL': External driver type (MSSQL, ODBC, OLEDB)
-- Output: Enables capturing __RowStatus and __ErrorMessage
-- EnableBulkMode: Improves performance with bulk batches (uses 10000 rows per batch rather than 200)

Bulk Mode - Insert Records with Lookup Field (Read from External Source)

INSERT INTO Account
SOURCE (
    'MSSQL',
    'Data Source=localhost;Initial Catalog=tempdb;Integrated Security=true',
    'SELECT TOP 1000000 
         Account_Name as Name,
         AccountOwnerId as [Owner.ExternalId]
     FROM very_large_staging_table'
)
WITH (
    Output = 1,
    EnableBulkMode = 1
)

-- Notes:
-- 'MSSQL': External driver type (MSSQL, ODBC, OLEDB)
-- Output: Enables capturing __RowStatus and __ErrorMessage
-- EnableBulkMode: Improves performance with bulk batches (uses 10000 rows per batch rather than 200)

Bulk Mode - Delete Large Volume of Data (Read IDs from External Source)

DELETE FROM Account
SOURCE (
    'MSSQL',
    'Data Source=localhost;Initial Catalog=tempdb;Integrated Security=true',
    'SELECT TOP 1000000 
         Account_ID as Id
     FROM very_large_staging_table'
)
WITH (
    Output = 1,
    EnableBulkMode = 1
)

-- Notes:
-- 'MSSQL': External driver type (MSSQL, ODBC, OLEDB)
-- Output: Enables capturing __RowStatus and __ErrorMessage
-- EnableBulkMode: Improves performance with bulk batches (uses 10000 rows per batch rather than 200)

Bulk Mode - Update Large Volume of Data (Read from External Source)

UPDATE Account
SOURCE (
    'MSSQL',
    'Data Source=localhost;Initial Catalog=tempdb;Integrated Security=true',
    'SELECT TOP 1000000 
         Account_ID as Id,
         Account_Name as Name,
         City as BillingCity
     FROM very_large_staging_table'
)
WITH (
    Output = 1,
    EnableBulkMode = 1
)

-- Notes:
-- 'MSSQL': External driver type (MSSQL, ODBC, OLEDB)
-- Output: Enables capturing __RowStatus and __ErrorMessage
-- EnableBulkMode: Improves performance with bulk batches (uses 10000 rows per batch rather than 200)

Bulk Mode - Update Lookup Field (Read from External Source)

UPDATE Account
SOURCE (
    'MSSQL',
    'Data Source=localhost;Initial Catalog=tempdb;Integrated Security=true',
    'SELECT TOP 1000000 
         Account_ID as Id,
         Account_Name as Name,
         AccountOwnerId as [Owner.ExternalId]
     FROM very_large_staging_table'
)
WITH (
    Output = 1,
    EnableBulkMode = 1
)

-- Notes:
-- 'MSSQL': External driver type (MSSQL, ODBC, OLEDB)
-- Output: Enables capturing __RowStatus and __ErrorMessage
-- EnableBulkMode: Improves performance with bulk batches (uses 10000 rows per batch rather than 200)

External Input from ODBC - Insert Multiple Rows from ODBC Source (e.g., CSV) into Salesforce

INSERT INTO Account
SOURCE (
    'ODBC',  -- External driver type: MSSQL, ODBC, or OLEDB
    'Driver={ZappySys CSV Driver};DataPath=c:\somefile.csv',  -- ODBC connection string
    '
    SELECT 
        Acct_Name AS Name,
        Billing_City AS BillingCity,
        Locations AS NumberofLocations__c
    FROM $
    WITH (
        -- Either use SRC to point to a file or use inline DATA. Comment out one as needed.
        
        -- Examples:
        -- SRC = ''c:\file_1.csv''
        -- SRC = ''c:\some*.csv''
        -- SRC = ''https://abc.com/api/somedata-in-csv''

        DATA = ''Acct_Name,Billing_City,Locations
        Account001,City001,1
        Account002,City002,2
        Account003,City003,3''
    )'
)
-- Notes:
-- Column aliases in SELECT must match Salesforce target fields.
-- Preview the Account object to verify available fields.

WITH (
    Output = 1,                -- Capture __RowStatus and __ErrorMessage for each record
    -- EnableBulkMode = 1,     -- Use Bulk API (recommended for 5,000+ rows)
    EnableParallelThreads = 1, -- Use multiple threads for real-time inserts
    MaxParallelThreads = 6     -- Set maximum number of threads
)

DML - Upsert Lookup Field Value Using External ID Instead of Salesforce ID

[relationship_name.external_id_field_name(child_object_name)]

Owner.SomeExternalId__c(User)

relationship_name.external_id_field_name

FieldName = null

AccountId = null

relation_name.external_id_name(target_table) = null

-- Upsert record into Salesforce Account object
UPSERT INTO Account (
    Name,
    BillingCity,
    [Owner.SomeExternalId__c(User)]  -- Use external ID field on related Owner (User) object
)
VALUES (
    'mycompany name',
    'New York',
    'K100'  -- External ID value of the User (Owner)
)
WITH (
    KEY = 'SupplierId__c',  -- External ID field used for UPSERT on Account object
    Output = 1              -- Return __RowStatus and __ErrorMessage for result diagnostics
)

Supported WITH Properties in BULK Mode

When using the ZappySys Salesforce ODBC Driver with BULK mode, you can pass additional options using the WITH clause to customize behavior.
Here are other supported properties commonly used BULK mode:

INSERT INTO Account/UPDATE Account/DELETE FROM Account
SOURCE(...)
WITH(
Output=1 /*Other values can be Output='*' , Output=1 , Output=0 , Output='Col1,Col2...ColN'.  When Output option is supplied then error is not thrown but you can capture status and message in __RowStatus and __ErrorMessage output columns*/
,EnableBulkMode=1 --use Job Style Bulk API (uses 10000 rows per batch rather than 200)
--,MaxRowsPerJob=500000 --useful to control memory footprint in driver
--,ConcurrencyMode='Default' /* or 'Parallel' or 'Serial' - Must set BulkApiVersion=2 to use this, Bulk API V1 doesnt support this yet. If you get locking errors then change to Serial*/
--,BulkApiVersion=2 --default is V1
--,IgnoreFieldsIfInputNull=1 --Set this option to True if you wish to ignore fields if input value is NULL. By default target field is set to NULL if input value is NULL.
--,FieldsToSetNullIfInputNull='SomeColum1,SomeColumn5,SomeColumn7' --Comma separated CRM entity field names which you like to set as NULL when input value is NULL. This option is ignored if IgnoreFieldsIfInputNull is not set to True.
--,AssignmentRuleId='xxxxx' --rule id to invoke on value assignment
--,UseDefaultAssignmentRule=1 --sets whether you like to use default rule
--,AllOrNone=1 --If true, any failed records in a call cause all changes for the call to be rolled back. Record changes aren't committed unless all records are processed successfully. The default is false. Some records can be processed successfully while others are marked as failed in the call results.
--,OwnerChangeOptions='option1,option2...optionN' -- use one or more options from below. Use '-n' suffix to disable option execution e.g. TransferOpenActivities-n
-->>> Available owner change options: EnforceNewOwnerHasReadAccess,TransferOpenActivities,TransferNotesAndAttachments,TransferOthersOpenOpportunities,TransferOwnedOpenOpportunities,TransferOwnedClosedOpportunities,TransferOwnedOpenCases,TransferAllOwnedCases,TransferContracts,TransferOrders,TransferContacts,TransferArticleOwnedPublishedVersion,TransferArticleOwnedArchivedVersions,TransferArticleAllVersions,KeepAccountTeam,KeepSalesTeam,KeepSalesTeamGrantCurrentOwnerReadWriteAccess,SendEmail
-->>> For more information visit https://zappysys.com/link/?id=10141
--,AllowFieldTruncation=1 --If true, truncate field values that are too long, which is the behavior in API versions 14.0 and earlier.
--,AllowSaveOnDuplicates=1 --Set to true to save the duplicate record. Set to false to prevent the duplicate record from being saved.
--,EnableParallelThreads=1 --Enables sending Data in multiple threads to speedup. This option is ignored when bulk mode enabled (i.e. EnableBulkMode=1)
--,MaxParallelThreads=6 --Maximum threads to spin off to speedup write operation. This option is ignored when bulk mode enabled (i.e. EnableBulkMode=1)
--,TempStorageMode='Disk' --or 'Memory'. Use this option to overcome OutOfMemory Error if you processing many rows. This option enables how Temp Storage is used for query processing. Available options 'Disk' or 'Memory' (Default is Memory)
)

More Examples and Documentation

Conclusion

In this article we showed you how to connect to Salesforce in Informatica and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys Salesforce Driver allows you to connect not only to Salesforce, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Salesforce Connector for Informatica and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Salesforce Connector for Informatica Documentation

More integrations

Other connectors for Informatica

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Azure DevOps

Cosmos DB

DropBox

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

Trino

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

Other application integration scenarios for Salesforce

SSIS

SQL Server

Power BI

SSRS

MS Access

MS Excel

SSAS

C#

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Common Searches: