![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Reckon, you gain database-like access to live Reckon data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Reckon as external data in MicroStrategy Web and creating a simple visualization of Reckon data.
The CData ODBC driver offers unmatched performance for interacting with live Reckon data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Reckon, the driver pushes supported SQL operations, like filters and aggregations, directly to Reckon and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Reckon data using native MicroStrategy data types.
Information for connecting to Reckon follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Reckon must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
When you are connecting to a local Reckon instance, you do not need to set any connection properties.
Requests to Reckon are made through the Remote Connector. The Remote Connector runs on the same machine as Reckon and accepts connections through a lightweight, embedded Web server. The server supports SSL/TLS, enabling users to connect securely from remote machines.
The first time you connect to your company file, authorize the Remote Connector with Reckon. See the "Getting Started" chapter of the help documentation for a guide.
When you configure the DSN, 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.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
If you are installing the CData ODBC Driver for Reckon in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
[CData Reckon Sys] Driver = CData ODBC Driver for Reckon Description = My Description User = RCUser Password = RCUserPassword URL = http://remotehost:8166
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Reckon data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
Using the CData ODBC Driver for Reckon in MicroStrategy Web, you can easily create robust visualizations and reports on Reckon data. Read our other articles on connecting to Reckon in MicroStrategy and connecting to Reckon in MicroStrategy Desktop for more examples.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.
Download a free trial of the Reckon ODBC Driver to get started:
Download NowLearn more:
๐ Reckon Accounting IconThe Reckon ODBC Driver is a powerful tool that allows you to connect with live data from Reckon directly from any applications that support ODBC connectivity.
Access Reckon data like you would a database - read, write, and update Customers, Transactions, Invoices, Sales Receipts, etc. through a standard ODBC Driver interface.