Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Provide OData Services of Microsoft Dataverse Data from a WCF Application
In this article, we will demonstrate the process of generating an OData feed for Microsoft Dataverse data by developing a WCF Service Application.
The CData ADO.NET Provider for Microsoft Dataverse enables you to rapidly develop service-oriented applications using the Windows Communication Foundation (WCF) framework, providing Microsoft Dataverse data data to OData consumers. This article guides you through creating an entity data model for connectivity and a WCF Data Service to expose OData services. You can then consume the feed with various OData clients, such as Power Pivot or applications using the CData ADO.NET Provider for OData.
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
Create the OData Service
Follow the steps below to create a WCF service application that will provide connectivity to Microsoft Dataverse data via OData.
- Open Visual Studio and create a new project. Select the WCF Service Application template.
- Delete the autogenerated IService.cs and Service1.svc.
- Install Entity Framework 6:
Use the Package Manager Console in Visual Studio to install the latest version of Entity Framework. Run the following command to download and install Entity Framework automatically:
Install-Package EntityFramework
- Register the Entity Framework provider:
- Add the following provider entry in the "providers" section of your App.config or Web.config file. This section should already exist if the Entity Framework installation was successful.
<configuration> ... <entityFramework> <providers> ... <provider invariantName="System.Data.CData.CDS" type="System.Data.CData.CDS.CDSProviderServices, System.Data.CData.CDS.Entities.EF6" /> </providers> </entityFramework> </configuration>
- Add a reference to System.Data.CData.CDS.Entities.dll, located in lib/4.0 in the installation directory.
- Build the project to complete the setup for using EF6.
- Add the following provider entry in the "providers" section of your App.config or Web.config file. This section should already exist if the Entity Framework installation was successful.
- Click Project -> Add New Item -> ADO.NET Entity Data Model.
- In the Entity Data Model wizard that is displayed, select the 'EF Designer from Database' option.
- In the resulting Choose Your Connection dialog, click New Connection.
In the Connection properties dialog, select the CData Microsoft Dataverse Data Source and enter the necessary credentials.
A typical connection string is below:
OrganizationUrl=https://myaccount.crm.dynamics.com/InitiateOAuth=GETANDREFRESH
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.
- Select Microsoft Dataverse tables and views that you want OData clients to access.
- Click Project -> Add New Item -> WCF Data Service.
Specify the data source class and configure access to the new WCF Data Service. In the example below, the Access Rule for the entities is set to All. This means that any user will be able to read and modify data.
using System; using System.Collections.Generic; using System.Data.Services; using System.Data.Services.Common; using System.Linq; using System.ServiceModel.Web; using System.Web; namespace CDSService{ public class CDSDataService : DataService<CDSEntities> { public static void InitializeService(DataServiceConfiguration config) { config.SetEntitySetAccessRule("*", EntitySetRights.All); config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V3; } } }
- Run the project. Applications that support OData can now access the Salesforce data and reflect any changes. You can access the feed in your browser. The feed will resemble the following:
Consume the OData Service from Power Pivot
You can now use the service from any OData client; for example, Excel Power Pivot.
- Open Excel and click on the Power Pivot Window button.
- A new pop-up will appear. Select the option From Data Feeds.
- In the resulting Table Import Wizard, enter the OData URL. For example, http://localhost:12449/CDSDataService.svc/.
- After connecting to the OData service, click the Next button at the bottom of the window.
- A table listing of the available tables will appear in the next window of the wizard. Select which tables you want to import and click Finish.
- Click Close to import the data in Power Pivot.