![]() |
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 Workday data from PostgreSQL. In this article, we walk through the process of connecting to Workday 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 Workday, allowing you to query data from Workday 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 Workday, leveraging server-side processing to return the requested Workday data quickly.
CData provides the easiest way to access and integrate live data from Workday. Customers use CData connectivity to:
Users frequently integrate Workday with analytics tools such as Tableau, Power BI, and Excel, and leverage our tools to replicate Workday data to databases or data warehouses. Access is secured at the user level, based on the authenticated user's identity and role.
For more information on configuring Workday to work with CData, refer to our Knowledge Base articles: Comprehensive Workday Connectivity through Workday WQL and Reports-as-a-Service & Workday + CData: Connection & Integration Best Practices.
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
To connect to Workday, users need to find the Tenant and BaseURL and then select their API type.
To obtain the BaseURL and Tenant properties, log into Workday and search for "View API Clients." On this screen, you'll find the Workday REST API Endpoint, a URL that includes both the BaseURL and Tenant.
The format of the REST API Endpoint is: https://domain.com/subdirectories/mycompany, where:
The value you use for the ConnectionType property determines which Workday API you use. See our Community Article for more information on Workday connectivity options and best practices.
| API | ConnectionType Value |
|---|---|
| WQL | WQL |
| Reports as a Service | Reports |
| REST | REST |
| SOAP | SOAP |
Your method of authentication depends on which API you are using.
See the Help documentation for more information on configuring OAuth with Workday.
๐ 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 Workday 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 Workday data:
CREATE EXTENSION tds_fdw;
CREATE SERVER "Workday1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'Workday1');
CREATE USER MAPPING for postgres SERVER "Workday1" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
CREATE SCHEMA "Workday1";
#Using a table_name definition: CREATE FOREIGN TABLE "Workday1".Workers ( id varchar, Legal_Name_Last_Name varchar) SERVER "Workday1" OPTIONS(table_name 'Workday.Workers', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "Workday1".Workers ( id varchar, Legal_Name_Last_Name varchar) SERVER "Workday1" OPTIONS (schema_name 'Workday', table_name 'Workers', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "Workday1".Workers ( id varchar, Legal_Name_Last_Name varchar) SERVER "Workday1" OPTIONS (query 'SELECT * FROM Workday.Workers', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "Workday1".Workers ( id varchar, col2 varchar OPTIONS (column_name 'Legal_Name_Last_Name')) SERVER "Workday1" OPTIONS (schema_name 'Workday', table_name 'Workers', row_estimate_method 'showplan_all');
SELECT id, Legal_Name_Last_Name FROM "Workday1".Workers;
Now, you have created a simple query from live Workday data. For more information on connecting to Workday (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Workday data in PostgreSQL.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial