How to connect to Salesforce Data Cloud (Data 360) in PowerShell

Introduction

You can connect to your Salesforce Data Cloud (Data 360) data from PowerShell via the high-performance Salesforce Data Cloud (Data 360) ODBC Driver (powered by ZappySys JDBC-ODBC Bridge Driver). We'll walk you through the entire setup.

Let's not waste time and get started!

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

• Minimum required version: Java 8
  • Amazon Corretto 8
  • Oracle JRE 8
• Recommended Java version: Java 21
  • Amazon Corretto 21
  • Oracle JRE 21

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

Download Salesforce Data Cloud (Data 360) JDBC driver

To connect to Salesforce Data Cloud (Data 360), you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

1. Visit Salesforce Data Cloud (Data 360) website or MVN Repository.

2. Select the appropriate JDBC driver version in Latest Versions section in MVN Repository:

   

3. Download the JDBC driver, and save it locally, e.g. to C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar.

   

4. Done! That was easy, wasn't it? Let's proceed to the next step.

Create data source using Salesforce Data Cloud (Data 360) ODBC Driver

Video instructions

Watch this quick walkthrough to see how to configure your Salesforce Data Cloud (Data 360) ODBC data source, or scroll down for the step-by-step written guide.

Step-by-step instructions

To get data from Salesforce Data Cloud (Data 360) using PowerShell, we first need to create an ODBC data source. We will later read this data in PowerShell. Perform these steps:

1. Download and install ODBC PowerPack (if you haven't already).

2. Search for odbc and open the ODBC Data Sources (64-bit):

   

3. Create a User data source (User DSN) based on the ZappySys JDBC Bridge Driver driver:

   ZappySys JDBC Bridge Driver

   
   • Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
   • Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this

4. Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

   SalesforceDataCloudData360DSN

   jdbc:salesforce-datacloud://login.salesforce.com

   com.salesforce.datacloud.jdbc.DataCloudJDBCDriver

   C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar

   optional for Salesforce Data Cloud (Data 360)

   optional for Salesforce Data Cloud (Data 360)

   optional for Salesforce Data Cloud (Data 360)

   

   For Production (login.salesforce.com), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Password:
   • Client ID (Consumer Key):
   • Client Secret (Consumer Secret):
   • Data space: default

     Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

     WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
     1. Sign in to Salesforce Setup as an administrator.
     2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

     3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
     4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
     5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
     6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
     7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
     8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

   For Sandbox (test.salesforce.com), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://test.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Password:
   • Client ID (Consumer Key):
   • Client Secret (Consumer Secret):
   • Data space: default

     Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

     WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
     1. Sign in to Salesforce Setup as an administrator.
     2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

     3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
     4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
     5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
     6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
     7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
     8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

   For JWT Bearer (External Client App), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Client ID (Consumer Key):
   • Private key (PEM):
   • Data space: default

     JWT Bearer Flow with an External Client App (current Salesforce recommendation for JDBC). No refresh-token dance; you still register the callback URL so the app is valid.

     1. Create an External Client App in Salesforce Setup. Enable OAuth and JWT Bearer.
     2. Callback URL must be exactly https://zappysys.com/oauth (do not use localhost or another capture URL).
     3. Upload or generate a certificate. Download the private key as PEM (-----BEGIN PRIVATE KEY-----).
     4. Copy the Consumer Key (Client ID).
     5. Paste Client ID, integration username, and the full PEM into this profile. Do not check a private key into source control.
     6. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     7. Done. You can query from C#, Python, PowerShell, and ODBC apps.

5. You should see a message saying that connection test is successful:

   

6. Otherwise, if you are getting an error, start by troubleshooting the JDBC connection with DBeaver in the section below:

   Jump to troubleshooter

7. We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:

   SalesforceDataCloudData360DSN

   SHOW TABLES

   

   SHOW TABLES

   You can also click on the <Select Table> dropdown and select a table from the list.

   The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the JDBC-ODBC Bridge Driver simply relays the SQL query without altering it.

   Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.

8. Click OK to finish creating the data source.

Read Salesforce Data Cloud (Data 360) data in PowerShell

Sometimes, you need to quickly access and work with your Salesforce Data Cloud (Data 360) data in PowerShell. Whether you need a quick data overview or the complete dataset, this article will guide you through the process. Here are some common scenarios:

• Quickly peek at Salesforce Data Cloud (Data 360) data
• Monitor data constantly in your console

• Export data to a CSV file so that it can be sliced and diced in Excel
• Export data to a JSON file so that it can ingested by other processes
• Export data to an HTML file for user-friendly view and easy sharing
• Create a schedule to make it an automatic process

• Store data internally for analysis or for further ETL processes
• Create a schedule to make it an automatic process

• Integrate data with other systems via external APIs

In this article, we will delve deeper into how to quickly view the data in PowerShell terminal and how to save it to a file. But let's stop talking and get started!

Reading individual fields

1. Open your favorite PowerShell IDE (we are using Visual Studio Code).

2. Use this code snippet to read the data using SalesforceDataCloudData360DSN data source:

   "DSN=SalesforceDataCloudData360DSN"

   

   For your convenience, here is the whole PowerShell script:

   # Configure connection string and query
   $connectionString = "DSN=SalesforceDataCloudData360DSN"
   $query = "SELECT * FROM Customers"
   
   # Instantiate OdbcDataAdapter and DataTable
   $adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
   $table = New-Object System.Data.DataTable
   
   # Fill the table with data
   $adapter.Fill($table)
   
   # Since we know we will be reading just 4 columns, let's define format for those 4 columns, each separated by a tab
   $format = "{0}`t{1}`t{2}`t{3}"
   
   # Display data in the console
   foreach ($row in $table.Rows)
   {
       # Construct line based on the format and individual Salesforce Data Cloud (Data 360) fields
       $line = $format -f ($row["CustomerId"], $row["CompanyName"], $row["Country"], $row["Phone"])
       Write-Host $line
   }
   

   Access specific Salesforce Data Cloud (Data 360) table field using this code snippet:

   $field = $row["ColumnName"]

   You will find more info on how to manipulate DataTable.Rows property in Microsoft .NET reference.
   For demonstration purposes we are using sample tables which may not be available in Salesforce Data Cloud (Data 360).

3. To read values in a console, save the script to a file and then execute this command inside PowerShell terminal:

   
   You can also use even a simpler command inside the terminal, e.g.:

   . 'C:\Users\john\Documents\dsn.ps1'

Retrieving all fields

However, there might be case, when you want to retrieve all columns of a query. Here is how you do it:

"DSN=SalesforceDataCloudData360DSN"

Again, for your convenience, here is the whole PowerShell script:

# Configure connection string and query
$connectionString = "DSN=SalesforceDataCloudData360DSN"
$query = "SELECT CustomerId, CompanyName, Country, Phone FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Display data in the console
foreach ($row in $table.Rows) {
    $line = ""
    foreach ($column in $table.Columns) {
        $value = $row[$column.ColumnName]

        # Let's handle NULL values
        if ($value -is [DBNull])
        {
            $value = "(NULL)"
        }
        $line += $value + "`t"
    }
    Write-Host $line
}

SELECT * FROM Customers LIMIT 10

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 JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

   ZappySys JDBC Bridge Driver - Salesforce Data Cloud (Data 360)

   Read Salesforce Data Cloud (Data 360) with SQL. Query data graphs and lake objects from Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools -- almost no coding required.

   SalesforceDataCloudData360DSN

   
2. The window opens, telling us the connection string was successfully copied to the clipboard:
3. Then just paste the connection string into your script:
4. You are good to go! The script will execute the same way as using a DSN.

Handling limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

1. Open your ODBC data source.
2. Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
3. Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
4. Continue by pasting the copied connection string into a newly created file and save it.
5. Finally, the last step! Just construct a shorter ODBC connection string using this format:

   DRIVER={ZappySys JDBC Bridge Driver};SettingsFile=C:\temp\odbc-connection-string.txt

6. Our troubles are over! Now you should be able to use this connection string in PowerShell with no problems.

Write Salesforce Data Cloud (Data 360) data to a file in PowerShell

Save data to a CSV file

Export data to a CSV file so that it can be sliced and diced in Excel:

# Configure connection string and query
$connectionString = "DSN=SalesforceDataCloudData360DSN"
$query = "SELECT * FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Export table data to a file
$table | ConvertTo-Csv -NoTypeInformation -Delimiter "`t" | Out-File "C:\Users\john\saved-data.csv" -Force

Save data to a JSON file

Export data to a JSON file so that it can ingested by other processes (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Json | Out-File "C:\Users\john\saved-data.json" -Force

Save data to an HTML file

Export data to an HTML file for user-friendly view and easy sharing (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Html | Out-File "C:\Users\john\saved-data.html" -Force

Troubleshooting

Validating JDBC connection in DBeaver

If you are experiencing JDBC connection issues, start by testing your JDBC driver in a JDBC client tool like DBeaver. If the JDBC connection fails in DBeaver, it naturally will not work in your ODBC data source either.

Create generic JDBC driver

1. Download and install DBeaver Community Edition.

2. Open DBeaver.

3. Click Database in the top menu and select Driver Manager:

   

4. Click the New button to start adding a custom JDBC driver:

   

5. Configure the connection settings by entering the Driver Name and Class Name (com.salesforce.datacloud.jdbc.DataCloudJDBCDriver):

   

   com.salesforce.datacloud.jdbc.DataCloudJDBCDriver

6. Go to the Libraries tab, click Add File, and select your Salesforce Data Cloud (Data 360) driver library file(s), e.g. C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar:

   
   Make sure to add all the required library dependencies.

7. Your JDBC driver jar library is now added:

   

   C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar

8. (Optional). If required by your JDBC driver, add additional properties by going to the Default properties tab, Right-clicking on the background, and selecting Add new property:

   

9. Click on a value to modify it, then click OK to finish:

   

We are now ready to test the connection. Let's proceed!

Test connection

1. Click the New Database Connection icon in the toolbar:

   

2. Select your newly created JDBC driver from the list and click Next:

   

3. Enter your JDBC URL (e.g. jdbc:salesforce-datacloud://login.salesforce.com), click Test Connection to verify it works, and then click Finish:

   

   jdbc:salesforce-datacloud://login.salesforce.com

4. Finally, expand the database and table list to check the connection status:

   

There are two possible outcomes from the connection test:

• Reason:
  The JDBC driver works perfectly, meaning the issue lies within your ODBC data source configuration.
• Action:
  Double-check your ODBC data source configuration and ensure it matches the settings that successfully connected in DBeaver.

• Reason:
  There is likely an issue with the JDBC driver configuration or the connection details provided.
• Action:
  Contact the ZappySys Support Team for assistance.

If you are still experiencing issues or need further help, please contact us:

Frequent issues and solutions

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

• How to combine multiple JAR files
  Learn how to merge multiple .jar dependencies when your JDBC driver requires more than one file.
• How to fix JBR error: “Data lake is not available / Unable to verify trust for server certificate chain”
  Resolve SSL or certificate validation issues encountered during JDBC connections.
• System Exception: “Java is not installed or not accessible”
  Fix Java path or environment issues that prevent the JDBC Bridge from launching Java.
• JDBC Bridge Driver disconnect from Java host error
  Troubleshoot unexpected disconnection problems between your client application and the Java process.
• Error: Could not open jvm.cfg while using JDBC Bridge Driver
  Resolve JVM configuration path errors during driver initialization.
• How to enable JDBC Bridge Driver logging
  Enable detailed driver logging for better visibility during troubleshooting.
• How to pass JDBC connection parameters (not by URL)
  Learn how to specify connection properties programmatically instead of embedding them in the JDBC URL.
• How to fix JDBC Bridge error: “No connection could be made because the target machine actively refused it”
  Troubleshoot firewall or local port binding issues preventing communication with the Java host.
• How to use JDBC Bridge options (System Property for Java command line, e.g., classpath, proxy)
  Configure custom Java options like classpath and proxy using JDBC Bridge system properties.

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Salesforce Data Cloud (Data 360) data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

• Centralized data access
  The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
• Centralized access control
  Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in PowerShell (client-side) to connect to it.

Let's not wait and get going!

Create Salesforce Data Cloud (Data 360) data source in the gateway

In this section we will create a data source for Salesforce Data Cloud (Data 360) in the Data Gateway. Let's follow these steps to accomplish that:

1. Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:

   

2. Go to the Users tab and follow these steps to add a Data Gateway user:

   • Click the Add button
   • In the Login field enter a username, e.g., john
   • Then enter a Password
   • Check the Is Administrator checkbox
   • Click OK to save
   

3. Now we are ready to add a data source:

   • Click the Add button
   • Give the Data source a name (have it handy for later)
   • Then select Native - ZappySys JDBC Bridge Driver
   • Finally, click OK
   SalesforceDataCloudData360DSN

   ZappySys JDBC Bridge Driver

   

4. When the ZappySys JDBC Bridge Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Salesforce Data Cloud (Data 360) ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:

   • Open ODBC data source configuration and click Copy settings:
     

     ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

     ZappySys JDBC Bridge Driver - Salesforce Data Cloud (Data 360)

     Read Salesforce Data Cloud (Data 360) with SQL. Query data graphs and lake objects from Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools -- almost no coding required.

     SalesforceDataCloudData360DSN

     
   • The window opens, telling us the connection string was successfully copied to the clipboard:

   • Then go to Data Gateway configuration and in data source configuration window click Load settings:

     SalesforceDataCloudData360DSN

     

     ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

     ZappySys JDBC Bridge Driver - Salesforce Data Cloud (Data 360)

     Read Salesforce Data Cloud (Data 360) with SQL. Query data graphs and lake objects from Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools -- almost no coding required.

     SalesforceDataCloudData360DSN

     
   • Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.

5. Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:

   
   • This will initially allow all inbound traffic.
   • Click Edit IP filters to restrict access to specific IP addresses or ranges.

6. Crucial Step: After creating or modifying the data source, you must:

   • Click the Save button to persist your changes.
   • Hit Yes when prompted to restart the Data Gateway service.

   This ensures all changes are properly applied:

   
   Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from PowerShell. To achieve that, let's perform these steps:

1. Search for odbc and open the ODBC Data Sources (64-bit):

   

2. Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

   ODBC Driver 17 for SQL Server

   
   If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.

3. Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

   ZappySysGatewayDSN

   localhost,5000

   
   Make sure you separate the hostname and port with a comma, e.g. localhost,5000.

4. Proceed with the authentication part:

   • Select SQL Server authentication
   • In the Login ID field enter the user name you created in the Data Gateway, e.g., john
   • Set Password to the one you configured in the Data Gateway
   

5. Then set the default database property to SalesforceDataCloudData360DSN (the one we used in the Data Gateway):

   SalesforceDataCloudData360DSN

   SalesforceDataCloudData360DSN

   
   Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).

6. Continue by checking the Trust server certificate option:

   

7. Once you do that, test the connection:

   

8. If the connection is successful, everything is good:

   

9. Done!

We are ready to move to the final step. Let's do it!

Access data in PowerShell via the gateway

Finally, we are ready to read data from Salesforce Data Cloud (Data 360) in PowerShell via the Data Gateway. Follow these final steps:

1. Go back to PowerShell.

2. Use this code snippet to read the data using ZappySysGatewayDSN data source:

   "DSN=ZappySysGatewayDSN"

   

   For your convenience, here is the whole PowerShell script:

   # Configure connection string and query
   $connectionString = "DSN=ZappySysGatewayDSN"
   $query = "SELECT * FROM Customers"
   
   # Instantiate OdbcDataAdapter and DataTable
   $adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
   $table = New-Object System.Data.DataTable
   
   # Fill the table with data
   $adapter.Fill($table)
   
   # Since we know we will be reading just 4 columns, let's define format for those 4 columns, each separated by a tab
   $format = "{0}`t{1}`t{2}`t{3}"
   
   # Display data in the console
   foreach ($row in $table.Rows)
   {
       # Construct line based on the format and individual Salesforce Data Cloud (Data 360) fields
       $line = $format -f ($row["CustomerId"], $row["CompanyName"], $row["Country"], $row["Phone"])
       Write-Host $line
   }
   

   Access specific Salesforce Data Cloud (Data 360) table field using this code snippet:

   $field = $row["ColumnName"]

   You will find more info on how to manipulate DataTable.Rows property in Microsoft .NET reference.
   For demonstration purposes we are using sample tables which may not be available in Salesforce Data Cloud (Data 360).

3. Read the data the same way we discussed at the beginning of this article.

4. That's it!

Now you can connect to Salesforce Data Cloud (Data 360) data in PowerShell via the ZappySys Data Gateway.