Ready to get started?

Learn more about the CData ADO.NET Provider for Workday or download a free trial:

Download Now

Access Workday Data with Entity Framework 6

This article shows how to access Workday data using an Entity Framework code-first approach. Entity Framework 6 is available in .NET 4.5 and above.

Entity Framework is an object-relational mapping framework that can be used to work with data as objects. While you can run the ADO.NET Entity Data Model wizard in Visual Studio to handle generating the Entity Model, this approach, the model-first approach, can put you at a disadvantage if there are changes in your data source or if you want more control over how the entities operate. In this article you will complete the code-first approach to accessing Workday data using the CData ADO.NET Provider.

  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 Workday Entity Framework 6 assembly and the connection string.

    To connect, there are three pieces of information required: Authentication, API URL, and WSDL URL.

    Authentication

    To authenticate, specify your User and Password. Note that you must append your Tenant to your User separated by an '@' character. For instance, if you normally log in with 'geraldg' and your Tenant is 'mycompany_mc1', then your User should be specified as 'geraldg@mycompany_mc1'.

    API URL

    The API URL may be specified either directly via APIURL, or it may be constructed from the Tenant, Service, and Host. The APIURL is constructed in the following format: <Host>/ccx/service/<Tenant>/<Service>.

    WSDL URL

    The WSDLURL may be specified in its entirety, or may be constructed from the Service and WSDLVersion connection properties. The WSDLURL is constructed in the following format: https://community.workday.com/sites/default/files/file-hosting/productionapi/<Service>/<WSDLVersion>/<Service>.wsdl <configuration> ... <connectionStrings> <add name="WorkdayContext" connectionString="Offline=False;User=myuser;Password=mypassword;Tenant=mycompany_gm1;Host=https://wd3-impl-services1.workday.com" providerName="System.Data.CData.Workday" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.Workday" type="System.Data.CData.Workday.WorkdayProviderServices, System.Data.CData.Workday.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>

  4. Add a reference to System.Data.CData.Workday.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 WorkdayContext. 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 WorkdayContext : DbContext { public WorkdayContext() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<WorkdayContext>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
  7. Create another .cs file and name it after the Workday entity you are retrieving, for example, Workers. 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("Workers")] public class Workers { [System.ComponentModel.DataAnnotations.Key] public System.String Worker_Reference_WID { get; set; } public System.String Legal_Name_Last_Name { get; set; } }
  8. Now that you have created an entity, add the entity to your context class: public DbSet<Workers> Workers { set; get; }
  9. With the context and entity finished, you are now ready to query the data in a separate class. For example: WorkdayContext context = new WorkdayContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.Workers select line;