Ready to get started?

Download a free trial of the Dynamics 365 Data Provider to get started:

 Download Now

Learn more:

Dynamics 365 Icon Dynamics 365 ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with Dynamics 365.

Build MVC Applications with Connectivity to Dynamics 365 Data



This article shows how to use only the Entity Framework and the CData ADO.NET provider to access Dynamics 365 from an ASP.NET MVC application.

In this article, we will guide you through the process of utilizing wizards within Visual Studio to seamlessly integrate the CData ADO.NET Provider for Dynamics 365 into a basic MVC (Model, View, Controller) project.

Create the Entity Framework Model

Follow the steps below to save connection properties and map tables to entities in the data model.

  1. Create a new MVC project in Visual Studio. In this example, the project name is MvcDynamics365App.
  2. If you are using Entity Framework 6, you will need to take the preliminary step of registering the Dynamics 365 Entity Framework provider for your project. See the "LINQ and Entity Framework" chapter in the help documentation for a guide.

    Note that MVC 3 scaffolding and MVC 4 scaffolding do not support Entity Framework 6. You can use your scaffolding with Entity Framework 6 by upgrading to the latest version of MVC.

  3. To add the .edmx file from the designer, right-click your Models folder and click Add New Item. Select ADO.NET Entity Data Model, name the model, and click Add. In this example, the name of the model is Dynamics365Model.
  4. In the Entity Data Model wizard, select the option 'EF Designer from database'. The Entity Data Model wizard is displayed.
  5. Click New Connection. Select CData Dynamics 365 Data Source in the dialog that is displayed.
  6. Specify the required connection string properties.

    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

    A typical connection string is below:

    OrganizationUrl=https://myaccount.operations.dynamics.com/;Edition=Sales;InitiateOAuth=GETANDREFRESH
  7. Name the connection and select whether to include sensitive information, such as connection credentials, in the connection string. For simplicity, this example saves sensitive information in Web.config. The connection settings are saved as Dynamics365Entities.

  8. Select the tables and views you need. In this example, GoalHeadings is imported. Also, the option to pluralize object names is deselected in this example. Click Finish to create the .edmx file.
  9. Build your project to complete this step.

Scaffold the Controller and Views

Once you've established the model and completed the project build, you can employ ASP.NET Scaffolding wizards to generate both the controller and the views.

  1. In Solution Explorer, right-click the controllers folder and click Add -> Controller. Select MVC 5 Controller with views, using Entity Framework.
  2. In the Add Controller dialog that is then displayed, select the following options:

    • Model class: Select a table you imported; for example, GoalHeadings.
    • Data context class: Select your context class.
  3. Leave the default values for the other fields.

You can now access the list of GoalHeadings records at http://MySite/GoalHeadings. Next to each record are links to edit, delete, and see more information. You can also create new GoalHeadings records. With every state change the site picks up any data changes.