![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Dynamics NAV, you gain database-like access to live Dynamics NAV data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Dynamics NAV as external data in MicroStrategy Web and creating a simple visualization of Dynamics NAV data.
The CData ODBC driver offers unmatched performance for interacting with live Dynamics NAV data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Dynamics NAV, the driver pushes supported SQL operations, like filters and aggregations, directly to Dynamics NAV 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 Dynamics NAV data using native MicroStrategy data types.
Information for connecting to Dynamics NAV follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Dynamics NAV must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
Before you can connect, OData Services will need to be enabled on the server. Once OData Services are enabled, you will be able to query any Services that are published on the server.
The User and Password properties, under the Authentication section, must be set to valid Dynamics NAV user credentials. In addition, specify a URL to a valid Dynamics NAV server organization root and a ServerInstance. If there is not a Service Default Company for the server, set the Company as well.
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 Dynamics NAV 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 DynamicsNAV Sys] Driver = CData ODBC Driver for Dynamics NAV Description = My Description http://myserver:7048 User = myserver\Administrator Password = admin ServerInstance = DYNAMICSNAV71
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 Dynamics NAV 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 Dynamics NAV in MicroStrategy Web, you can easily create robust visualizations and reports on Dynamics NAV data. Read our other articles on connecting to Dynamics NAV in MicroStrategy and connecting to Dynamics NAV 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 Dynamics NAV ODBC Driver to get started:
Download NowLearn more:
๐ Dynamics NAV IconThe Dynamics NAV ODBC Driver is a powerful tool that allows you to connect with live Dynamics NAV data, directly from any applications that support ODBC connectivity.
Access Dynamics NAV like you would a database - read, write, and update Items, Sales Orders, Purchase Orders, etc. through a standard ODBC Driver interface.