The Lyftron Provider for Sage 300 offers the most natural way to access Sage 300 data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Sage 300 data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Sage 300 data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Sage 300.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Sage 300, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your Sage 300 connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Sage 300 for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Sage 300 connection with Lyftron."User=SAMPLE;Password=password;URL=http://127.0.0.1/Sage300WebApi/v1/-/;Company=SAMINC;"
|Connection Name||Enter your connection details||Required|
|User||your Sage 300 SAMPLE||Required|
|Password||your Sage 300 Password||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Tables are retrieved dynamically from the authenticated Sage 300 account.
Child TablesChild tables are also retrieved, which contain child objects of their parents. For example, OEOrders has OEOrders_OrderCommentsInstructions and OEOrders_OrderDetails as its child tables. These tables are exposed as aggregate columns while querying their parent table. They also have references to the unique identifier of their parent.
Read-only views are retrieved dynamically from the authenticated Sage 300 account.
Stored Procedures Stored Procedures
Stored Procedures are function-like interfaces to Sage 300. Stored procedures allow you to execute operations to Sage 300.
Collaborative Query Processing
The provider offloads as much of the SELECT statement processing as possible to Sage 300 and then processes the rest of the query in memory. API limitations and requirements are also documented in this section.
See SupportEnhancedSQL for more information on how the provider circumvents API limitations with in-memory client-side processing.
SELECT statements for the main tables are mostly supported server-side. For example:
Note: When executing SELECT statements on child tables, everything is processed client side
Lists the available tables.
The following query retrieves the available tables:
|CatalogName||String||The database containing the table.|
|SchemaName||String||The schema containing the table.|
|TableName||String||The name of the table.|
|TableType||String||The table type.|
|Description||String||A description of the table.|