Initial JDBC Bridge catalog version. Hands-free Maven JAR download. Auth Notes and SQL examples for ODBC apps. 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.
]]> 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.
]]> 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.
]]> Lists tables available to this connection. Use this in Power BI or a SQL Server Linked Server to confirm the catalog before building reports.

]]> Returns rows from my_catalog.MyTable. Replace the identifier with your catalog object. Works in Excel, SSRS, and Crystal Reports.

]]> Returns matching rows from my_catalog.MyTable. Swap the column and literal for your schema.

]]> Joins two tables on a key. Use in Azure Data Factory or SSIS when you need a combined extract.

]]> Counts rows per group. Typical Power BI import pattern before a visual.

]]> Keeps groups whose count is at least 10.

]]> = 10]]> Returns the first 100 rows ordered by a column. Useful for preview in Excel or Crystal Reports.

]]> Returns the number of rows in my_catalog.MyTable.

]]> Maps a column to labels with CASE.

]]> Returns a column list instead of star. Prefer this in Linked Server views.

]]>