![]() |
VOOZH | about |
The CData ADO.NET Provider for Clio is fully integrated into the SAP Crystal Reports for Visual Studio development environment. You can employ standard ADO.NET components to construct reports, much like you would with SQL Server, but with the added advantage of real-time connectivity to Clio. This article will guide you through the essential three steps to incorporate Clio data into a report that refreshes upon opening.
Note: You will need to install SAP Crystal Reports, developer version for Visual Studio to follow this tutorial.
To follow this article, you will also need a Visual Studio Crystal Reports project. This article will add a report to a WPF application. You can create one by clicking File -> New Project and then selecting the Crystal Reports WPF Application template. In the resulting wizard, select the option to create a blank report.
Creating an ADO.NET data source for Clio from Server Explorer makes it easy to create a DataSet that can be used in Crystal Reports wizards and the Crystal Reports Designer. You can find a guide to working with Clio data in Server Explorer in the "Getting Started" chapter of the help documentation.
Start by setting the Profile connection property to the location of the Clio Profile on disk (e.g. C:\profiles\Clio.apip). Next, set the ProfileSettings connection property to the connection string for Clio (see below).
Clio uses OAuth-based authentication.
First, register an OAuth application with Clio. You can do so by logging to your Developer Account and clicking the Add button. Enter details and select the scope of your application here - these details will be shown to Clio users when they're asked to authorize your application. Your Oauth application will be assigned a client id (key) and a client secret (secret). Additionally set the Region in ProfileSettings connection property.
After setting the following connection properties, you are ready to connect:
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.
Follow the steps below to use the Visual Studio ADO.NET DataSet Designer to create an ADO.NET DataSet object. Crystal Reports will bind to the DataSet object, which contains Clio table metadata. Note that this approach also adds a connection string to App.config; you will use this connection string later to load data into the report.
Follow the steps below to add columns from the DataSet to the report:
Having created the DataSet, which will only contain the metadata, you will now need to create the DataTable containing the actual data. You can use the APIDataAdapter to fill a DataTable with the results of an SQL query.
<startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup>
Add the following references in your Window.xaml.cs file:
using System.Configuration; using CrystalDecisions.CrystalReports.Engine; using CrystalDecisions.Shared; using System.Data.CData.API; using System.Data;
Add the following Window_Loaded method in your Window.xaml.cs to execute the SQL query that will return the DataTable. Note that your query needs to select at least the same columns used in your report.
private void Window_Loaded(object sender, RoutedEventArgs e) {
ReportDocument report = new ReportDocument();
report.Load("../../CrystalReport1.rpt");
var connectionString = ConfigurationManager.ConnectionStrings["MyAppConfigConnectionStringName"].ConnectionString;
using (APIConnection connection = new APIConnection(connectionString)) {
APIDataAdapter dataAdapter = new APIDataAdapter(
"SELECT Id, Total FROM Bills WHERE State = 'awaiting_payment'", connection);
DataSet set = new DataSet("_set");
DataTable table = set.Tables.Add("_table");
dataAdapter.Fill(table);
report.SetDataSource(table);
}
reportViewer.ViewerCore.ReportSource = report;
}
In the Window.xaml file, add the Loaded event so that your Window tag resembles the following:
<Window x:Class="CrystalReportWpfApplication4.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:cr="clr-namespace:SAPBusinessObjects.WPF.Viewer;assembly=SAPBusinessObjects.WPF.Viewer" Title="WPF Crystal Report Viewer" Height="600" Width="800" Loaded="Window_Loaded"> ... </Window>
You can also use the DataSet with experts like the Chart Expert:
Note that Crystal Reports performs the aggregation on the data already loaded into DataTable, instead of, for example, executing a GROUP BY to the Clio API. This will also be true for the report creation wizards.
You could gain more control over the queries executed to Clio by creating another DataSet and populating it with a different query. See the help documentation for more information on the driver's SQL engine.
👁 DataSet columns to be added to a chart. (Salesforce is shown.)Connect to live data from Clio with the API Driver
Connect to Clio