![]() |
VOOZH | about |
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 Dynamics 365 data from PostgreSQL. In this article, we walk through the process of connecting to Dynamics 365 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 Dynamics 365, allowing you to query data from Dynamics 365 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 Dynamics 365, leveraging server-side processing to return the requested Dynamics 365 data quickly.
CData simplifies access and integration of live Microsoft Dynamics 365 data. Our customers leverage CData connectivity to:
CData customers use our Dynamics 365 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 Dynamics 365 data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.
For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.
OrganizationUrl is the URL to your Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com
๐ Configuring a connection (Salesforce is shown)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.
With the connection configured and a PAT generated, you are ready to connect to Dynamics 365 data from PostgreSQL.
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).
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 installNote: 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=
sudo service postgresql start
psql -h localhost -U postgres -d postgresNote: Instead of localhost you can put the IP where your PostgreSQL is hosted.
After you have installed the extension, follow the steps below to start executing queries to Dynamics 365 data:
CREATE EXTENSION tds_fdw;
CREATE SERVER "Dynamics3651" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'Dynamics3651');
CREATE USER MAPPING for postgres SERVER "Dynamics3651" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
CREATE SCHEMA "Dynamics3651";
#Using a table_name definition: CREATE FOREIGN TABLE "Dynamics3651".GoalHeadings ( id varchar, Name varchar) SERVER "Dynamics3651" OPTIONS(table_name 'Dynamics365.GoalHeadings', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "Dynamics3651".GoalHeadings ( id varchar, Name varchar) SERVER "Dynamics3651" OPTIONS (schema_name 'Dynamics365', table_name 'GoalHeadings', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "Dynamics3651".GoalHeadings ( id varchar, Name varchar) SERVER "Dynamics3651" OPTIONS (query 'SELECT * FROM Dynamics365.GoalHeadings', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "Dynamics3651".GoalHeadings ( id varchar, col2 varchar OPTIONS (column_name 'Name')) SERVER "Dynamics3651" OPTIONS (schema_name 'Dynamics365', table_name 'GoalHeadings', row_estimate_method 'showplan_all');
SELECT id, Name FROM "Dynamics3651".GoalHeadings;
Now, you have created a simple query from live Dynamics 365 data. For more information on connecting to Dynamics 365 (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Dynamics 365 data in PostgreSQL.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial