Rapidly Develop Salesforce Data 360-Driven Apps with Active Query Builder

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Leverage the Active Query Builder SQL interface and .NET data access to create data-driven WinForms and ASP.NET apps backed by Salesforce Data 360.

Write standard .NET to expose Salesforce Data 360 data through an SQL interface: Active Query Builder helps developers write SQL interfaces; the CData ODBC Driver for Salesforce Data 360 enables standards-based access to Salesforce Data 360. This integration uses the Microsoft ADO.NET Provider for ODBC as a bridge between the ODBC Driver and the Active Query Builder objects to build a visual SQL composer.

Connect to Salesforce Data 360 as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Salesforce Data 360 supports authentication via the OAuth standard.

OAuth

Set AuthScheme to OAuth.

Desktop Applications

CData provides an embedded OAuth application that simplifies authentication at the desktop.

You can also authenticate from the desktop via a custom OAuth application, which you configure and register at the Salesforce Data 360 console. For further information, see Creating a Custom OAuth App in the Help documentation.

Before you connect, set these properties:

  • InitiateOAuth: GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
  • OAuthClientId (custom applications only): The Client ID assigned when you registered your custom OAuth application.
  • OAuthClientSecret (custom applications only): The Client Secret assigned when you registered your custom OAuth application.

When you connect, the driver opens Salesforce Data 360's OAuth endpoint in your default browser. Log in and grant permissions to the application.

The driver then completes the OAuth process as follows:

  • Extracts the access token from the callback URL.
  • Obtains a new access token when the old one expires.
  • Saves OAuth values in OAuthSettingsLocation so that they persist across connections.
  • For other OAuth methods, including Web Applications and Headless Machines, refer to the Help documentation.

    Use SQL to Interact with Salesforce Data 360

    Follow the steps below to create a WinForms visual query builder.

    1. Open Active Query Builder for .NET WinForms. Opening Active Query Builder.
    2. In the new Windows Forms project go to the "File" menu and click "Connect..."
    3. Under Database Connections, click "Add..." Adding a new Connection.
    4. Set your desired Connection Name (e.g. CData Salesforce Data 360), set Connection Type to "ODBC" and locate your previously configured DSN in the "User/System" DSN dropdown. Selecting a previously configured DSN (Amazon Athena is shown).
    5. Click "OK" to save the new connection.
    6. Back in the Database Connection wizard, select the newly created connection and click "OK." A newly added Connection (Amazon Athena is shown).
    7. Click "File" > "New Query" to create a QueryBuilder

    You can now build queries visually: Double-click a table in the Columns Pane Area and an entity/relationship diagram is displayed in the Query Building Area. Columns that you select in the diagram are added to the query.

    Building queries interactively with Active Query Builder.

Ready to get started?

Download a free trial of the Salesforce Data Cloud ODBC Driver to get started:

 Download Now

Learn more:

Salesforce Data Cloud Icon Salesforce Data 360 ODBC Driver

The Salesforce Data 360 ODBC Driver is a powerful tool that allows you to connect with live data from Salesforce Data 360, directly from any applications that support ODBC connectivity.

Access Salesforce Data 360 data like you would a database - read Salesforce Data 360 DataGraph, DataLakeObject, DataModelObjects, CalculatedInsights, etc. through a standard ODBC Driver interface.