VOOZH about

URL: https://www.cdata.com/kb/tech/dataverse-cloud-postgres.rst

โ‡ฑ Connect to Live Microsoft Dataverse Data in PostGresSQL Interface through CData Connect AI


Connect to Live Microsoft Dataverse Data in PostGresSQL Interface through CData Connect AI

๐Ÿ‘ Dibyendu Datta
Dibyendu Datta
Lead Technology Evangelist
Create a live connection to Microsoft Dataverse in CData Connect AI and connect to your Microsoft Dataverse data from PostgreSQL.

There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect AI, you gain database-like access to live Microsoft Dataverse data from PostgreSQL. In this article, we walk through the process of connecting to Microsoft Dataverse data in Connect AI and establishing a connection between Connect AI and PostgreSQL using a TDS foreign data wrapper (FDW).

CData Connect AI provides a pure SQL Server interface for Microsoft Dataverse, allowing you to query data from Microsoft Dataverse without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Microsoft Dataverse, leveraging server-side processing to return the requested Microsoft Dataverse data quickly.

About Microsoft Dataverse Data Integration

CData provides the easiest way to access and integrate live data from Microsoft Dataverse (formerly the Common Data Service). Customers use CData connectivity to:

  • Access both Dataverse Entities and Dataverse system tables to work with exactly the data they need.
  • Authenticate securely with Microsoft Dataverse in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
  • Use SQL stored procedures to manage Microsoft Dataverse entities - listing, creating, and removing associations between entities.

CData customers use our Dataverse connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources)or analyze live Dataverse data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).


Getting Started


Connect to Microsoft Dataverse in Connect AI

CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. ๐Ÿ‘ Adding a Connection
  3. Select "Microsoft Dataverse" from the Add Connection panel
  4. ๐Ÿ‘ Selecting a data source
  5. Enter the necessary authentication properties to connect to Microsoft Dataverse.

    You can connect without setting any connection properties for your user credentials. Below are the minimum connection properties required to connect.

    • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
    • OrganizationUrl: Set this to the organization URL you are connecting to, such as https://myorganization.crm.dynamics.com.
    • Tenant (optional): Set this if you wish to authenticate to a different tenant than your default. This is required to work with an organization not on your default Tenant.

    When you connect the Common Data Service OAuth endpoint opens in your default browser. Log in and grant permissions. The OAuth process completes automatically.

    ๐Ÿ‘ Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab in the Add Microsoft Dataverse Connection page and update the User-based permissions. ๐Ÿ‘ Updating permissions

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. ๐Ÿ‘ Creating a new PAT
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to Microsoft Dataverse data from PostgreSQL.

Build the TDS Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).

  1. You can clone and build the git repository via something like the following view source:
    sudo apt-get install git
    git clone https://github.com/tds-fdw/tds_fdw.git
    cd tds_fdw
    make USE_PGXS=1
    sudo make USE_PGXS=1 install
    
    Note: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG=
  2. After you finish the installation, then start the server:
    sudo service postgresql start
    
  3. Then go inside the Postgres database
    psql -h localhost -U postgres -d postgres
    
    Note: Instead of localhost you can put the IP where your PostgreSQL is hosted.

Connect to Microsoft Dataverse data as a PostgreSQL Database and query the data!

After you have installed the extension, follow the steps below to start executing queries to Microsoft Dataverse data:

  1. Log into your database.
  2. Load the extension for the database:
    CREATE EXTENSION tds_fdw;
    
  3. Create a server object for Microsoft Dataverse data:
    CREATE SERVER "CDS1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'CDS1');
    
  4. Configure user mapping with your email and Personal Access Token from your Connect AI account:
    CREATE USER MAPPING for postgres SERVER "CDS1" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
    
  5. Create the local schema:
    CREATE SCHEMA "CDS1";
    
  6. Create a foreign table in your local database:
    #Using a table_name definition:
    
    CREATE FOREIGN TABLE "CDS1".Accounts ( 
    id varchar, 
    Name varchar) 
    SERVER "CDS1"
    OPTIONS(table_name 'CDS.Accounts', row_estimate_method 'showplan_all');
    
    #Or using a schema_name and table_name definition:
    
    CREATE FOREIGN TABLE "CDS1".Accounts ( 
    id varchar, 
    Name varchar) 
    SERVER "CDS1"
    OPTIONS (schema_name 'CDS', table_name 'Accounts', row_estimate_method 'showplan_all');
    
    #Or using a query definition:
    
    CREATE FOREIGN TABLE "CDS1".Accounts (
    id varchar, 
    Name varchar) 
    SERVER "CDS1"
    OPTIONS (query 'SELECT * FROM CDS.Accounts', row_estimate_method 'showplan_all');
    
    #Or setting a remote column name:
    
    CREATE FOREIGN TABLE "CDS1".Accounts (
    id varchar,
    col2 varchar OPTIONS (column_name 'Name'))
    SERVER "CDS1"
    OPTIONS (schema_name 'CDS', table_name 'Accounts', row_estimate_method 'showplan_all');
    
  7. You can now execute read/write commands to Microsoft Dataverse:
    SELECT id, Name
    FROM "CDS1".Accounts;
    

More Information & Free Trial

Now, you have created a simple query from live Microsoft Dataverse data. For more information on connecting to Microsoft Dataverse (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Microsoft Dataverse data in PostgreSQL.