![]() |
VOOZH | about |
This article illustrates using the Sage Intacct ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Sage Intacct data to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.
CData provides the easiest way to access and integrate live data from Sage Intact. Customers use CData connectivity to:
Users frequently integrate Sage Intact with analytics tools such as Tableau, Power BI, and Excel, and leverage our tools to replicate Workday data to databases or data warehouses.
To learn about how other customers are using CData's Sage Intacct solutions, check out our blog: Drivers in Focus: Accounting Connectivity.
In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.
๐ The components used in the data task in this example.In the connection manager, enter the connection details for Sage Intacct data.
To connect using the Login method, the following connection properties are required: User, Password, CompanyId, SenderId and SenderPassword.
User, Password, and CompanyId are the credentials for the account you wish to connect to.
SenderId and SenderPassword are the Web Services credentials assigned to you by Sage Intacct.
๐ Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT Name, TotalDue FROM Customer
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
๐ Input and destination columns in the OLE DB Destination Editor.Download a free trial of the Sage Intacct Data Provider to get started:
Download NowLearn more:
๐ Sage Intacct IconComplete read-write access to Sage Intacct enables developers to search (Contacts, Invoices, Transactions, Vendors, etc.), update items, edit customers, and more, from any .NET application.