Evaluating Mercury with your Own GP Data

Evaluating Mercury with your Own GP Data

This article assumes that you have already installed Mercury.   

 

Mercury comes with a handful of sample reports, including several that use Dynamics GP data from our Test-and-Demo server on the web. 

 

Redirecting these reports to use your own GP server is simple. 

 

Every Mercury report is associated with a data “Connection” that specifies a server and a database.  All of the sample GP reports use the same data Connection. 

 

So, all you have to do is edit one Connection, changing the properties so that the connection points to your server (and desired company database) instead of ours, and you’re done!  Your sample GP reports will instantly use your own data. 

 

For complete information on creating and editing Connections, see the Mercury documentation on Admin > Connections 

 

In the Mercury main window: 

 

 

  1. Click on Admin Tools in the Settings ribbon. 

  1. Click Connections. 

  1. Click on the “GP1” connection to select it.  The connection’s properties are displayed in the lower grid. 

  1. Click the “Edit” button on the toolstrip. 

  1. Optional, but recommended: edit the connection’s description so that it’s meaningful in your context. 

  1. Change various connection properties. 

    1. Data Source = your GP server name or IP address 

    2. Initial Catalog = your GP Company database name 

    3. Integrated Security: if you use Windows Authentication to access your database, change this to Yes -- and you're done.  The user who runs Mercury must have appropriate select permissions on the views and tables used in these reports. 

Otherwise, leave Integrated Security as “No” and also change these: 

  1. User ID = a valid SQL login-name on your server 

  1. Password = the password associated with the SQL login 

To simplify your evaluation, we suggest that you create a new SQL Login and add it to the DYNGRP role in the GP database.  You can delete the login at the end of the evaluation. 

The password is masked, and it is also encrypted before being saved with the Connection.

  1. Click the “Save” toolstrip button when you’re done. 

 

Here’s an example showing edited values for the GP1 connection, just prior to saving. 

 


    • Related Articles

    • Evaluating Mercury with your Own BC Data

      This article assumes that you have already installed Mercury.   Mercury comes with a handful of sample reports, including several that use Dynamics 365. These BC sample reports all use a data “Connection” that points to the Mercury’s own BC-Online ...

    • Microsoft Dynamics GP Actions

      By using Mercury "Actions" in a report based on a Dynamics GP database, you can: Open an underlying GP form associated with the data (a drillback) Open an attached document. Each of these features is discussed in detail below. For a general overview ...

    • Data Providers

      A “Data Provider” designates the specific database, file-type, or other data source that Mercury can use to retrieve data for your reports. When you create a Connection to a particular data source, you choose the Data Provider. See Admin > ...

    • Installing Mercury

      Requirements Microsoft Windows 64-bit (Windows 7 or higher) .NET Desktop Runtime 6.02 or higher (can be automatically installed with Mercury if needed) If installing on a server: Windows Server 2016 or higher If you’re installing a trial version, ...

    • Mercury Overview

      What is Mercury? Mercury is a general-purpose reporting and analysis tool that works with a variety of databases - for example: SQL Server, MySQL, Business Central (and other OData sources), CSV files, and others. Reporting and analysis are no longer ...