How to Access Monday.com 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 Monday.com 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 Monday.com Entity Framework 6 assembly and the connection string.

   You can connect to Monday.com using either API Token authentication or OAuth authentication.

   Connecting with an API Token

   Connect to Monday.com by specifying the APIToken. Set the AuthScheme to Token and obtain the APIToken as follows:

   • API tokens for admin users
     1. Log in to your Monday.com account and click on your avatar in the bottom left corner.
     2. Select Admin.
     3. Select "API" on the left side of the Admin page.
     4. Click the "Copy" button to copy the user's API token.
   • API tokens for non-admin users
     1. Click on your profile picture in the bottom left of your screen.
     2. Select "Developers"
     3. Click "Developer" and then "My Access Tokens" at the top.
     4. Select "Show" next to the API token, where you'll be able to copy it.

   Connecting with OAuth Authentication

   Alternatively, you can establish a connection using OAuth (refer to the OAuth section of the Help documentation).

   <configuration>
    ... 
    <connectionStrings>
    <add name="MondayContext" connectionString="Offline=False;APIToken=eyJhbGciOiJIUzI1NiJ9.yJ0aWQiOjE0MTc4NzIxMiwidWlkIjoyNzI3ODM3OSwiaWFkIjoiMjAyMi0wMS0yMFQxMDo0NjoxMy45NDFaIiwicGV;" providerName="System.Data.CData.Monday" />
    </connectionStrings>
    <entityFramework>
    <providers>
    ... 
    <provider invariantName="System.Data.CData.Monday" type="System.Data.CData.Monday.MondayProviderServices, System.Data.CData.Monday.Entities.EF6" />
    </providers>
    <entityFramework>
   </configuration>
   </code> 
   

4. Add a reference to System.Data.CData.Monday.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 MondayContext. 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 MondayContext : DbContext {
    public MondayContext() { }
   
    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
    // To remove the requests to the Migration History table
    Database.SetInitializer<MondayContext>(null); 
    // To remove the plural names 
    modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
    } 
   }
   

7. Create another .cs file and name it after the Monday.com entity you are retrieving, for example, Invoices. 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("Invoices")]
   public class Invoices {
    [System.ComponentModel.DataAnnotations.Key] 
    public System.String Id { get; set; }
    public System.String DueDate { get; set; }
   }
    
   

8. Now that you have created an entity, add the entity to your context class:

   public DbSet<Invoices> Invoices { set; get; }
   

9. With the context and entity finished, you are now ready to query the data in a separate class. For example:

   MondayContext context = new MondayContext();
   context.Configuration.UseDatabaseNullSemantics = true;
   var query = from line in context.Invoices select line;