How to Access Dynamics 365 Data Using Entity Framework

Microsoft Entity Framework serves as an object-relational mapping framework for working with data represented as objects. Although Visual Studio offers the ADO.NET Entity Data Model wizard to automatically generate the Entity Model, this model-first approach may present challenges when your data source undergoes changes or when you require greater control over entity operations. In this article, we will delve into the code-first approach for accessing Dynamics 365 data through the CData ADO.NET Provider, providing you with more flexibility and control.

1. Open Visual Studio and create a new Windows Form Application. This article uses a C# project with .NET 4.5.
2. Run the command 'Install-Package EntityFramework' in the Package Manger Console in Visual Studio to install the latest release of Entity Framework.

3. Modify the App.config file in the project to add a reference to the Dynamics 365 Entity Framework 6 assembly and the connection string.

   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

   <configuration> ... <connectionStrings> <add name="Dynamics365Context" connectionString="Offline=False;OrganizationUrl=https://myaccount.operations.dynamics.com/;Edition=Sales;InitiateOAuth=GETANDREFRESH" providerName="System.Data.CData.Dynamics365" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.Dynamics365" type="System.Data.CData.Dynamics365.Dynamics365ProviderServices, System.Data.CData.Dynamics365.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
4. Add a reference to System.Data.CData.Dynamics365.Entities.EF6.dll, located in the lib -> 4.0 subfolder in the installation directory.
5. Build the project at this point to ensure everything is working correctly. Once that's done, you can start coding using Entity Framework.
6. Add a new .cs file to the project and add a class to it. This will be your database context, and it will extend the DbContext class. In the example, this class is named Dynamics365Context. The following code example overrides the OnModelCreating method to make the following changes:
   • Remove PluralizingTableNameConvention from the ModelBuilder Conventions.
   • Remove requests to the MigrationHistory table.
   using System.Data.Entity; using System.Data.Entity.Infrastructure; using System.Data.Entity.ModelConfiguration.Conventions; class Dynamics365Context : DbContext { public Dynamics365Context() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<Dynamics365Context>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
7. Create another .cs file and name it after the Dynamics 365 entity you are retrieving, for example, GoalHeadings. In this file, define both the Entity and the Entity Configuration, which will resemble the example below: using System.Data.Entity.ModelConfiguration; using System.ComponentModel.DataAnnotations.Schema; [System.ComponentModel.DataAnnotations.Schema.Table("GoalHeadings")] public class GoalHeadings { [System.ComponentModel.DataAnnotations.Key] public System.String GoalHeadingId { get; set; } public System.String Name { get; set; } }
8. Now that you have created an entity, add the entity to your context class: public DbSet<GoalHeadings> GoalHeadings { set; get; }
9. With the context and entity finished, you are now ready to query the data in a separate class. For example: Dynamics365Context context = new Dynamics365Context(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.GoalHeadings select line;