![]() |
VOOZH | about |
In this article, we will guide you through the deployment process of the CData ADO.NET Provider for Sugar CRM on an SQL Server Reporting Services (SSRS) report server. Additionally, you will learn how to establish a shared data source, which facilitates connectivity to real-time Sugar CRM data from various reports. You can then access these shared data sources from the Report Designer within Visual Studio. For detailed instructions on creating datasets in Report Designer using ADO.NET, please refer to the "Using ADO.NET" section in the help documentation.
The provider installation automatically deploys the provider on report servers in native mode. On report servers in SharePoint mode, you can use the install-sprs.ps1 PowerShell script to deploy. Simply run the script from the lib subfolder in the installation directory, or pass in the "path" parameter.
You can create shared data sources directly from a report server or SharePoint site. Alternatively, you can use Report Designer to create shared data sources.
You can use Report Designer to create shared data sources on native mode report servers and report servers on a SharePoint server farm.
User=MyUser;Password=MyPassword;URL=MySugarCRMAccountURL;CacheMetadata=True;
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.
When you configure the connection, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
👁 Properties to define a shared data source in Report Designer. (Salesforce is shown.)On native mode installations of report server, you can use Report Manager to create shared data sources. You must have permissions to manage data sources on the report server.
User=MyUser;Password=MyPassword;URL=MySugarCRMAccountURL;CacheMetadata=True;
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.
👁 Properties to define a shared data source in Report Manager. (Salesforce is shown.)Follow the steps below to create a shared data source on a SharePoint site. Note that this step has the following prerequisites in SharePoint 2013:
Follow the steps below to add the report server content types to your library:
You can then create the shared data source. You will create an .rsds file that contains the connection information to Sugar CRM.
User=MyUser;Password=MyPassword;URL=MySugarCRMAccountURL;CacheMetadata=True;
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.
👁 Properties to define a shared data source in SharePoint. (Salesforce is shown.)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!