![]() |
VOOZH | about |
SQL Server Analysis Services (SSAS) serves as an analytical data engine employed in decision support and business analytics, offering high-level semantic data models for business reports and client applications like Power BI, Excel, Reporting Services reports, and various data visualization tools. When coupled with the CData ADO.NET Provider for Dynamics 365, you gain the capability to generate cubes from Dynamics 365 data, facilitating more profound and efficient data analysis.
In this article, we will guide you through the process of developing and deploying a multi-dimensional model of Dynamics 365 data by creating an Analysis Services project in Visual Studio. To proceed, ensure that you have an accessible SSAS instance and have installed the ADO.NET Provider.
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.).
Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for Dynamics 365 data in the project.
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
When you configure the connection, 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.
π Setting the Connection properties (Salesforce is shown.)After you create the data source, create the data source view.
Based on the foreign key match scheme, relationships in the underlying data will be automatically detected. You can view (and edit) these relationships by double clicking Data Source View.
π Discovered relationships in the data source view (Salesforce is shown).Note that adding a secondary data source to the Data Source View is not supported. When working with multiple data sources, SSAS requires both sources to support remote queries via OpenRowset which is unavailable in the ADO.NET Provider.
The last step before you can process the project and deploy Dynamics 365 data to SSAS is creating the cubes.
With the data source, data source view, and cube created, you are ready to deploy the cube to SSAS. To configure the target server and database, right-click the project and select properties. Navigate to deployment and configure the Server and Database properties in the Target section.
π Configuring the target server and database.After configuring the target server and database, right-click the project and select Process. You may need to build and deploy the project as a part of this step. Once the project is built and deployed, click Run in the Process Database wizard.
Now you have an OLAP cube for Dynamics 365 data in your SSAS instance, ready to be analyzed, reported, and viewed. Get started with a free, 30-day trial of the CData ADO.NET Provider for Dynamics 365.
Download a free trial of the Dynamics 365 Data Provider to get started:
Download NowLearn more:
π Dynamics 365 IconRapidly create and deploy powerful .NET applications that integrate with Dynamics 365.