![]() |
VOOZH | about |
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 QuickBooks data through the CData ADO.NET Provider, providing you with more flexibility and control.
CData simplifies access and integration of live QuickBooks data. Our customers leverage CData connectivity to:
Customers regularly integrate their QuickBooks data with preferred tools, like Power BI, Tableau, or Excel, and integrate QuickBooks data into their database or data warehouse.
Modify the App.config file in the project to add a reference to the QuickBooks Entity Framework 6 assembly and the connection string.
When you are connecting to a local QuickBooks instance, you do not need to set any connection properties.
Requests are made to QuickBooks through the Remote Connector. The Remote Connector runs on the same machine as QuickBooks and accepts connections through a lightweight, embedded Web server. The server supports SSL/TLS, enabling users to connect securely from remote machines.
The first time you connect, authorize the Remote Connector with QuickBooks. See the "Getting Started" chapter of the help documentation for a guide.
<configuration> ... <connectionStrings> <add name="QuickBooksContext" connectionString="Offline=False;URL=http://remotehost:8166;User=admin;Password=admin123;" providerName="System.Data.CData.QuickBooks" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.QuickBooks" type="System.Data.CData.QuickBooks.QuickBooksProviderServices, System.Data.CData.QuickBooks.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
using System.Data.Entity;
using System.Data.Entity.Infrastructure;
using System.Data.Entity.ModelConfiguration.Conventions;
class QuickBooksContext : DbContext {
public QuickBooksContext() { }
protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
// To remove the requests to the Migration History table
Database.SetInitializer<QuickBooksContext>(null);
// To remove the plural names
modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
}
}
using System.Data.Entity.ModelConfiguration;
using System.ComponentModel.DataAnnotations.Schema;
[System.ComponentModel.DataAnnotations.Schema.Table("Customers")]
public class Customers {
[System.ComponentModel.DataAnnotations.Key]
public System.String Name { get; set; }
public System.String CustomerBalance { get; set; }
}
public DbSet<Customers> Customers { set; get; }
QuickBooksContext context = new QuickBooksContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.Customers select line;
Download a free trial of the QuickBooks Data Provider to get started:
Download NowLearn more:
👁 QuickBooks IconComplete read-write access to QuickBooks enables developers to search (Customers, Transactions, Invoices, Sales Receipts, etc.), update items, edit customers, and more, from any .NET application.