Salesforce Connector for Power BI

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 Power BI without coding. We will use high-performance Salesforce Connector to easily connect to Salesforce and then access the data inside Power BI.

Let's follow the steps below to see how we can accomplish that!

Download Documentation

Video Tutorial - Integrate Salesforce data in Power BI

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

  • How to download and install the required PowerPack for Salesforce integration in Power BI
  • How to configure the connection for Salesforce
  • Features of the ZappySys Salesforce Driver (Authentication / Query Language / Examples / Driver UI)
  • How to use the Salesforce in Power BI

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

Step-by-step instructions

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

  1. Download and install ODBC PowerPack.

  2. Open ODBC Data Sources (x64):

    Open ODBC Data Source
  3. Create a User data source (User DSN) based on ZappySys Salesforce Driver

    ZappySys Salesforce Driver
    Create new User DSN for 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.
    Power BI uses a Service Account, when a solution is deployed to production environment, therefore for production environment you have to create and use a System DSN.
  4. Now, we need SalesForce Connection. Lets create it. ODBC SalesForce Driver - Create Connection

  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%'
    ZappySys ODBC Driver - Select Table and Preview Data
  6. Click OK to finish creating the data source

Video Tutorial

Read Salesforce data in Power BI using ODBC

Importing Salesforce data into Power BI from table or view

  1. Once you open Power BI Desktop click Get Data to get data from ODBC:
    Power Bi Get Data

  2. A window opens, and then search for "odbc" to get data from ODBC data source:
    Power Bi ODBC Get Data

  3. Another window opens and asks to select a Data Source we already created. Choose SalesforceDSN and continue:

    SalesforceDSN
    Power Bi Select ZappySys Driver DSN

  4. Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:

    SalesforceDSN
    Power Bi DSN Authentication

  5. Finally, you will be asked to select a table or view to get data from. Select one and load the data!
    Power Bi Load DSN Table Data

  6. Finally, finally, use extracted data from Salesforce in a Power BI report:
    Power Bi Extracted DSN Table Data

Importing Salesforce data into Power BI using SQL query

If you wish to import Salesforce data from SQL query rather than a table then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.

SalesforceDSN
SELECT * FROM Tickets
Get REST API data in Power BI Desktop using SQL query and ODBC
Consider using Custom Objects feature in ODBC data source to encapsulate SQL query in a Virtual Table. This way, you can see a virtual table in Power BI table list where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL query.

Using a full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

  1. Open ODBC data source configuration and click Copy settings:
    ZappySys Salesforce Driver - Salesforce
    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).
    SalesforceDSN
    Copy connection string for ODBC application
  2. The window opens, telling us the connection string was successfully copied to the clipboard: Successful connection string copying for ODBC application
  3. Then just paste the connection string into your script:
    SalesforceDSN
    DRIVER={ZappySys Salesforce Driver};Url='https://login.salesforce.com/services/Soap/u/{version}';Scopes='full offline_access';UserName='john.smith@my-company.com';Password='my-password';SecurityToken='my-security-token'
    Use full connection string in Power BI Desktop to read API data
  4. You are good to go! The script will execute the same way as using a DSN.
The DSN defined in the Data source name (DSN) field will be ignored.

Editing query for table in Power BI

There will be a time you need to change the initial query after importing data into Power BI. Don't worry, just right-click on your table and click Edit query menu item:

Edit query in Power BI to get REST API data
Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using parameters in Power BI (dynamic query)

In the real world, many values of your REST / SOAP API call may be coming from parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

To use a parameter in Power BI report, follow these simple steps:

  1. Firstly, you need to Edit query of your table (see previous section)

  2. Then just create a new parameter by clicking Manage Parameters dropdown, click New Parameter option, and use it in the query:

    						
                                = Odbc.Query("dsn=SalesforceDSN",
                                             "SELECT ProductID, ProductName, UnitPrice, UnitsInStock
                                              FROM Products
                                              WHERE UnitPrice > " & Text.From(MyParameter) & "
                                              ORDER BY UnitPrice")
                            
                    
    Use parameter in Power BI to get REST API data
    Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using DirectQuery Option rather than Import

So far we have seen how to Import Salesforce data into Power BI, but what if you have too much data and you don't want to import but link it. Power BI Offers very useful feature for this scenario. It's called DirectQuery Option. In this section we will explore how to use DirectQuery along with ZappySys Drivers.

Out of the box ZappySys Drivers won't work in ODBC Connection Mode, so you have to use SQL Server Connection rather than ODBC if you wish to use Live data using DirectQuery option. See below step-by-step instructions to enable DirectQuery mode in Power BI for Salesforce data.

Basically we will use ZappySys Data Gateway its part of ODBC PowerPack. We will then use Linked Server in SQL Server to Link API Service, then issue OPENROWSET queries from Power BI to SQL Server, and it will then call Salesforce via ZappySys Data Gateway.

  1. First, create a data source in ZappySys Data Gateway and create a Linked Server based on it.
  2. Once SQL Server Linked Server is configured we are ready to issue a SQL query in Power BI.
  3. Click Get Data in Power BI, select SQL Server Database
  4. Enter your server name and any database name
  5. Select Mode as DirectQuery
  6. Click on Advanced and enter query like below (we are assuming you have created Salesforce Data Source in Data Gateway and defined linked server - change the name below).
    SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_IN_GATEWAY], 'SELECT * FROM Tickets')
    SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_IN_GATEWAY], 'SELECT * FROM Tickets')
    DirectQuery option for Power BI (Read Salesforce Data Example using SQL Server Linked Server and ZappySys Data Gateway)


    DirectQuery option for Power BI (Read Salesforce Data Example using SQL Server Linked Server and ZappySys Data Gateway)

  7. Click OK and Load data... That's it. Now your Salesforce API data is linked rather than imported.

Publishing Power BI report to Power BI service

Here are the instructions on how to publish a Power BI report to Power BI service from Power BI Desktop application:

  1. First of all, go to Power BI Desktop, open a Power BI report, and click Publish button:

    Publish Power BI report to Power BI service
  2. Then select the Workspace you want to publish report to and hit Select button:

    Publish Power BI report to workspace
  3. Finally, if everything went right, you will see a window indicating success:

    Successful Power BI report publishing

    If you need to periodically refresh Power BI semantic model (dataset) to ensure data accuracy and up-to-dateness, you can accomplish that by using Microsoft On-premises data gateway. Proceed to the next section - Refreshing Power BI semantic model (dataset) using On-premises data gateway - and learn how to do that.

Refreshing Power BI semantic model (dataset) using On-premises data gateway

Power BI allows to refresh semantic models which are based on data sources that reside on-premises. This can be achieved using Microsoft On-premises data gateway. There are two types of On-premises gateways:

  • Standard Mode
  • Personal Mode

Standard Mode supports Power BI and other Microsoft Data Fabric services. It fits perfectly for Enterprise solutions as it installs as a Windows Service and also supports Direct Query feature.

Personal Mode, on the other hand, can be configured faster, but is designed more for home users (you cannot install it as a Windows Service and it does not support DirectQuery). You will find a detailed comparison in the link above.

We recommend to go with Personal Mode for a quick POC solution, but use Standard Mode in production environment.

Below you will find instructions on how to refresh semantic model using both types of gateways.

Refresh using On-premises data gateway (standard mode)

Here are the instructions on how to refresh a Power BI semantic model using On-premises data gateway (standard mode):

  1. Go to Power BI My workspace, hover your mouse cursor on your semantic model and click Settings:

    Configure Power BI semantic model settings
  2. If you see this view, it means you have to install On-premises data gateway (standard mode):

    On-premises data gateway is not installed
  3. Install On-premises data gateway (standard mode) and sign-in:

    signing in into on-premises data gateway standard
    Use the same email address you use when logging in into Power BI account.
  4. Register a new gateway (or migrate an existing one):

    registering or migrating on-premises data gateway standard
  5. If you are creating a new gateway, name your gateway, enter a Recovery key, and click Configure button:

    naming on-premises data gateway standard
  6. Now, let's get back to your semantic model settings in Power BI portal. Refresh the page and you should see your newly created gateway. Click arrow icon and then click on Add to gateway link:

    ODBC{"connectionstring":"dsn=SalesforceDSN"}
    Using On-premises Data Gateway Standard for Power BI Semantic Model
  7. Once you do that, you will create a new gateway connection. Give it a name, set Authentication method, Privacy level, and click Create button:

    dsn=SalesforceDSN
    Create new connection in Power BI On-premises data gateway
    In this example, we used the least restrictive Privacy level.

    If your connection uses a full connection string you may hit a length limitation when entering it into the field. To create the connection, you will need to shorten it manually. Check the section about the limitation of a full connection string on how to accomplish it.

    On-premises data gateway (personal mode) does not have this limitation.

  8. Proceed by choosing the newly created connection:

    ODBC{"connectionstring":"dsn=SalesforceDSN"}
    Selecting gateway connection in Power BI semantic model
  9. Finally, you are at the final step where you can refresh the semantic model:

    Refreshing Power BI semantic model using On-premises Data Gateway

Refresh using On-premises data gateway (personal mode)

Here are the instructions on how to refresh a Power BI semantic model using On-premises data gateway (personal mode):

  1. Go to Power BI My workspace, hover your mouse cursor on your semantic model and click Settings:

    Configure Power BI semantic model settings
  2. If you see this view, it means you have to install On-premises data gateway (personal mode):

    On-premises data gateway is not installed
  3. Install On-premises data gateway (personal mode) and sign-in:

    Sign-in to On-premises data gateway personal
    Use the same email address you use when logging in into Power BI account.
  4. Again, go to your semantic model Settings, expand Data source credentials, click Edit credentials, select Authentication method together with Privacy level, and then click Sign in button:

    dsn=SalesforceDSN
    Use On-premises data gateway personal for Power BI semantic model
  5. Finally, you are ready to refresh your semantic model:

    Refreshing Power BI semantic model using On-premises Data Gateway

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

This example demonstrates how to use the EnableBulkMode option to insert a large volume of records into Salesforce using the Bulk API (Job-based mode). By default, the standard mode writes data in batches of 200 rows. However, when Bulk API mode is enabled, it can send up to 10,000 rows per batch, offering better performance for large datasets. Note that using Bulk API mode may not provide performance benefits for small datasets (e.g., a few hundred rows).

In this example, the driver type is set to MSSQL. For other data sources such as CSV, REST API, or Oracle, update the driver type to ODBC and modify the connection string and query accordingly.

Ensure that your source query returns column names that match the target Salesforce object fields. The EXTERNAL option is used to map Salesforce target fields based on the output of the source query.

Important: If you’re using Windows authentication, the service account running the ZappySys Data Gateway must have the appropriate permissions on the source system.

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)

This example demonstrates how to use the EnableBulkMode option to insert a large number of records into Salesforce using the Bulk API (Job-based mode). Additionally, it shows how to set a lookup field—specifically the Owner field—by referencing an external ID from the User object instead of using the internal Salesforce ID.

If you are performing an Update operation, you must include the Id field in the source data. If your source field has a different name, alias it to Id in the SQL query. For Upsert operations, you can specify a custom external ID field using the Key='ExternalId_Field_Name' option. However, for standard Update operations, the Id field is mandatory.

By default, data is written in batches of 200 rows. When Bulk API mode is enabled, up to 10,000 rows can be sent per batch. This improves performance for large datasets, but offers little advantage for smaller volumes.

In this example, the driver type is set to MSSQL. For other sources such as CSV, REST API, or Oracle, change the driver type to ODBC and adjust the connection string and query accordingly.

Make sure the query outputs column names that match the target fields in the Salesforce object. The EXTERNAL option is used to map input columns to Salesforce fields dynamically.

Important: If you’re using Windows authentication, ensure that the service account running the ZappySys Data Gateway has the appropriate access permissions on the source system.

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)

This example demonstrates how to use the EnableBulkMode option to delete a large number of records from Salesforce using the Bulk API (Job-based mode). To perform a delete operation, the source query must return the Id column. If your source column has a different name, make sure to alias it as Id in the SQL query.

By default, data is processed in batches of 200 rows. When Bulk API mode is enabled, batches can include up to 10,000 rows, which significantly improves performance when working with large datasets. However, for small volumes (a few hundred records), Bulk API mode may not offer a noticeable performance benefit.

In this example, the driver type is set to MSSQL. For other data sources such as CSV, REST API, or Oracle, set the driver type to ODBC and update the connection string and query as needed.

Ensure that the query output includes column names that match the target Salesforce object fields. The EXTERNAL option allows dynamic mapping of input columns to Salesforce fields based on the source query.

Important: If you’re using Windows authentication, make sure the service account running the ZappySys Data Gateway has the necessary permissions to access the data 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)

This example illustrates how to use the EnableBulkMode option to update a large number of records in Salesforce via the Bulk API (Job-based mode). When performing an Update operation, the source query must include the Id column. If the source column is named differently, be sure to alias it as Id in your SQL query.

By default, records are processed in batches of 200 rows. When Bulk API mode is enabled, batches can handle up to 10,000 rows, which greatly improves performance for large datasets. However, for smaller datasets (e.g., a few hundred records), Bulk API may not offer a significant performance boost.

In this example, the driver type is set to MSSQL. For other sources such as CSV, REST API, or Oracle, change the driver type to ODBC and modify the connection string and query accordingly.

Ensure that your query returns column names matching the fields in the Salesforce target object. The EXTERNAL option is used to dynamically map input columns to Salesforce fields based on the query output.

Important: When using Windows authentication, the service account running the ZappySys Data Gateway must have the necessary permissions on the source system.

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)

This example shows how to use the EnableBulkMode option to update a large number of Salesforce records using the Bulk API (Job-based mode). In this scenario, we update a lookup field—specifically the Owner field—by referencing the external ID from the User object instead of using the internal Salesforce ID.

When performing an Update, the Id field must be included in the source data. If your source column has a different name, alias it as Id in the SQL query. For Upsert operations, you can specify a custom external ID using the Key='ExternalId_Field_Name' option. However, for standard Update operations, the Id field is required.

By default, the system processes 200 rows per batch. When EnableBulkMode is enabled, it can process up to 10,000 rows per batch, offering improved performance for large datasets. This mode is less effective for smaller data volumes.

In this example, the driver type is set to MSSQL. For other data sources (e.g., CSV, REST API, Oracle), change the driver type to ODBC and update the connection string and query as needed.

Ensure the query returns column names that match the fields in the target Salesforce object. The EXTERNAL option dynamically maps input columns to Salesforce fields based on the query output.

Important: If using Windows authentication, ensure the service account running the ZappySys Data Gateway has appropriate permissions on the source system.

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

This example demonstrates how to perform an INSERT operation in Salesforce using multiple input rows from an external data source such as MSSQL, ODBC, or OLEDB. The operation reads records via an external query and inserts them directly into Salesforce.

In this example, the driver type is set to MSSQL. For other systems like CSV, REST API, or Oracle, set the driver type to ODBC and update the connection string and query accordingly.

Ensure that the query returns column names that match the fields in the Salesforce target object. The EXTERNAL option is used to map these input columns to the corresponding Salesforce fields based on the source query output.

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

This example demonstrates how to set a lookup field value in Salesforce using an external ID rather than the internal Salesforce ID during DML operations such as INSERT, UPDATE, or UPSERT.

Typically, updating a lookup field requires the Salesforce ID of the related record. However, Salesforce also allows referencing a related record using an external ID field. To do this, use the following field name syntax:

[relationship_name.external_id_field_name(child_object_name)]
  • relationship_name: The API name of the relationship (e.g., Owner or YourObject__r).
  • external_id_field_name: A custom field on the related object, marked as External ID.
  • child_object_name (optional): The API name of the related object. If omitted, Salesforce derives it from the relationship name (without the __r suffix).

Example:

To assign a record owner using a custom external ID on the User object:

Owner.SomeExternalId__c(User)
  • Owner: The relationship name for the user record.
  • SomeExternalId__c: A custom external ID field in the User object.
  • User: The related (child) object name.

If you’re using the SOURCE(...) clause to read input data and enabling BulkApiMode=1 in the WITH(...) clause, you can omit the child object name. In that case, use the format:

relationship_name.external_id_field_name

Setting a Field to NULL:

To set a lookup or standard field to null, use:

FieldName = null

For example:

AccountId = null

Avoid using:

relation_name.external_id_name(target_table) = null

More Information:
For full details and examples, visit the official guide: ZappySys Docs - External ID in Lookup Fields

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

For additional examples and detailed guidance on using the ZappySys Salesforce ODBC Driver, visit the official documentation:

ZappySys Salesforce ODBC Driver – Online Help

Conclusion

In this article we showed you how to connect to Salesforce in Power BI 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 Power BI 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 Power BI Documentation

More integrations

Other connectors for Power BI

All
Big Data & NoSQL
Database
CRM & ERP
Marketing
Collaboration
Cloud Storage
Reporting
Commerce
API & Files

Other application integration scenarios for Salesforce

All
Data Integration
Database
BI & Reporting
Productivity
Programming Languages
Automation & Scripting
ODBC applications

  • How to connect Salesforce in Power BI?

  • How to get Salesforce data in Power BI?

  • How to read Salesforce data in Power BI?

  • How to load Salesforce data in Power BI?

  • How to import Salesforce data in Power BI?

  • How to pull Salesforce data in Power BI?

  • How to push data to Salesforce in Power BI?

  • How to write data to Salesforce in Power BI?

  • How to POST data to Salesforce in Power BI?

  • Call Salesforce API in Power BI

  • Consume Salesforce API in Power BI

  • Salesforce Power BI Automate

  • Salesforce Power BI Integration

  • Integration Salesforce in Power BI

  • Consume real-time Salesforce data in Power BI

  • Consume real-time Salesforce API data in Power BI

  • Salesforce ODBC Driver | ODBC Driver for Salesforce | ODBC Salesforce Driver | SSIS Salesforce Source | SSIS Salesforce Destination

  • Connect Salesforce in Power BI

  • Load Salesforce in Power BI

  • Load Salesforce data in Power BI

  • Read Salesforce data in Power BI

  • Salesforce API Call in Power BI