Learn more
 

Ready to get started?

Download a free trial of the Sage 300 Data Provider to get started:

 Download Now

Learn more:

Sage 300 Icon Sage 300 ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with Sage 300.

In this article

Related articles

LINQ to Sage 300 Data


LINQ offers versatile querying capabilities within the .NET Framework (v3.0+), offering a straightforward method for programmatic data access through CData ADO.NET Data Providers. In this article, we demonstrate the use of LINQ to retrieve information from the Sage 300 Data Provider.

This article illustrates using LINQ to access tables within the Sage 300 via the CData ADO.NET Data Provider for Sage 300. To achieve this, we will use LINQ to Entity Framework, which facilitates the generation of connections and can be seamlessly employed with any CData ADO.NET Data Providers to access data through LINQ.

See the help documentation for a guide to setting up an EF 6 project to use the provider.

  1. In a new project in Visual Studio, right-click on the project and choose to add a new item. Add an ADO.NET Entity Data Model.
  2. Choose EF Designer from Database and click Next.
  3. Add a new Data Connection, and change your data source type to "CData Sage 300 Data Source".

  4. Enter your data source connection information.

    Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.

    • Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the option under Security Groups (per each module required).
    • Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
    • Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.

    Authenticate to Sage 300 using Basic authentication.

    Connect Using Basic Authentication

    You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.

    • Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
    • User: Set this to the username of your account.
    • Password: Set this to the password of your account.

    Below is a typical connection string:

    User=SAMPLE;Password=password;URL=http://127.0.0.1/Sage300WebApi/v1/-/;Company=SAMINC;
  5. If saving your entity connection to App.Config, set an entity name. In this example we are setting Sage300Entities as our entity connection in App.Config.
  6. Enter a model name and select any tables or views you would like to include in the model.

Using the entity you created, you can now perform select commands. For example:

Sage300Entities context = new Sage300Entities(); var oeinvoicesQuery = from oeinvoices in context.OEInvoices select oeinvoices; foreach (var result in oeinvoicesQuery) { Console.WriteLine("{0} {1} ", result.Id, result.InvoiceUniquifier); }

See "LINQ and Entity Framework" chapter in the help documentation for example queries of the supported LINQ.