![]() |
VOOZH | about |
The CData JDBC driver for Dynamics 365 enables you to provide access to Dynamics 365 data across the enterprise. This article shows how to deploy the driver on JasperReports server and create a simple report based on a reporting domain, a business view of Dynamics 365 data.
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.).
Follow the steps below to deploy the driver JAR on JasperReports Server. The instructions below contain specifics for Dynamics 365 and the Tomcat server bundled with JasperReports Server. If you are using JBoss AS 7 instead of Tomcat, you can follow the standard process to deploy the Dynamics 365 JDBC Driver on JBoss.
Navigate to apache-tomcat -> webapps -> jasperserver-pro -> META-INF and add the following resource entry to the context.xml file:
<Resource name="jdbc/dynamics365" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.dynamics365.Dynamics365Driver" url="jdbc:dynamics365:OrganizationUrl=https://myaccount.operations.dynamics.com/;Edition=Sales;InitiateOAuth=GETANDREFRESH;" maxActive="20" maxIdle="10" maxWait="-1" factory="com.jaspersoft.jasperserver.tomcat.jndi.JSCommonsBasicDataSourceFactory"/>
Specify the required connection properties in the JDBC URL -- the url attribute.
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
For assistance in constructing the JDBC URL, use the connection string designer built into the Dynamics 365 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.dynamics365.jar
Fill in the connection properties and copy the connection string to the clipboard.
π Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
Dynamics 365 data JSP jdbc/dynamics365 javax.sql.DataSource Container
Follow the steps below to map the Dynamics 365 JDBC driver to a JDBC data source:
A domain is a metadata and access-control layer that surfaces a relevant business view to report creators. Follow the steps below to select Dynamics 365 columns, apply filters, and execute SQL to create a domain.
SELECT GoalHeadingId, Name FROM GoalHeadings WHERE Name = 'MyAccount'
After you have created a domain, you are ready to connect to data. Follow the steps below to create an Ad Hoc View in the Ad Hoc Editor.
You can now create reports hosted on JasperSoft Server. To do so from the Ad Hoc Editor, click Save Ad Hoc View and click Create Report.
π A report based on live data. (Salesforce is shown.)Download a free trial of the Dynamics 365 Driver to get started:
Download NowLearn more:
π Dynamics 365 IconRapidly create and deploy powerful Java applications that integrate with Dynamics 365.