![]() |
VOOZH | about |
This article illustrates using the Sugar CRM ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Sugar CRM 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.
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 Sugar CRM data.
The User and Password properties, under the Authentication section, must be set to valid SugarCRM user credentials. This will use the default OAuth token created to allow client logins. OAuthClientId and OAuthClientSecret are required if you do not wish to use the default OAuth token.
You can generate a new OAuth consumer key and consumer secret in Admin -> OAuth Keys. Set the OAuthClientId to the OAuth consumer key. Set the OAuthClientSecret to the consumer secret.
Additionally, specify the URL to the SugarCRM account.
Note that retrieving SugarCRM metadata can be expensive. It is advised that you store the metadata locally as described in the "Caching Metadata" chapter of the help documentation.
๐ Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT Name, AnnualRevenue FROM Accounts
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 Sugar Data Provider to get started:
Download NowLearn more:
๐ Sugar IconRapidly create and deploy powerful .NET applications that integrate with Sugar account data including Leads, Contacts, Opportunities, Accounts, and more!