Select Reports from the Admin Tools ribbon at the top of the application.
This opens the report in the Edit Report window with all its details and properties.
Some properties cannot be changed: Report-type, Report Source and Connection. Changing any of these requires creating a new report.
If the report has any Favorites (saved by any user) that include layouts, these layouts will be discarded in order to edit the report fields. (The Favorite’s saved Parameter values, if any, are preserved – only the layout will be lost.) Mercury warns you with a banner in the Fields tab and requires that you Enable Editing to continue. See the Pivot Reports Information>Favorites or Table Reports Information > Favorites articles for more on favorites.
Mercury can apply a unique color to reports in the Main Report List of each User. Click on Generate Legend Colors to access a drop-down with two options.
Some operations (deleting and exporting) can be done for multiple reports at once.
Mercury offers two kinds of exports.
Crystal |
🗸 |
🗸 |
The parameters tab determines how the user running the report will be prompted for parameter values used by a data query. This tab may vary somewhat based on the nature of the query (a stored procedure vs a view or a statement). If the query is a stored procedure, parameters are determined by the author. Otherwise, the Mercury user creating or editing the report can choose any report field(s) to be used as parameters by checking the box.
Refer to the table below for more information on each column. Each item represents a parameter that is used by the Database Query to supply data for the report.
Table
Pivot
Add Unbound Field or Sparkline
Delete Unbound Field or Sparkline
Hide all FilterArea Fields
Up and Down Arrows
An "Unbound Field" is also known as a "Calculated Field". It is a new Field created using Fields from the original data source. Because it isn’t part of the original data source, it’s not tied or "bound" to a data-source field.
When you create an Unbound Field, you provide Mercury with a calculation, a formula that defines how the field’s value is determined.
This button is enabled only when an Unbound field is selected. Be sure to save the report when you’re done creating or editing it!
To change the order in which a field appears on the report:
Select the field that you wish to move by clicking anywhere in the row.
Use the Up-Arrow / Down-Arrow buttons above the Fields grid, located to the right of the Delete Unbound Field or Sparkline button.
Click on to shift the field one position towards the right.
Click on to shift the field one position to the left
These controls have the effect of changing the field’s visible order in the Layout. This can also be achieved by editing the Visible Order Field Detail directly. See below for more information on this and other columns in the Fields grid.
When a data retrieval query returns multiple distinct result-sets (tables), Mercury numbers each to identify which one a field belongs. How the tables relate is defined in the Relations tab where the association between two of the tables is represented on each row. This Property applies only to Table-reports as Pivot-reports use just the first table.
Relationships are composed of:
A Parent record can have 0, 1, or many Children. A Child record has exactly one Parent record.
The example below shows a report that includes three tables arranged in three levels of hierarchy. Table#1 is the parent of Table#2. In turn, Table#2 serves as the parent of Table#3. This results in a three-level report.
Refer to the table below for more information on each column.
An Action provides a way, from within a Mercury report, to “do something” based on a particular data row or cell. Actions are available only in Table-reports.
An Action might consist of opening an external document attached to your data – say, a spec sheet on one of your products, or a sales invoice. Or an Action might involve invoking an underlying application and opening one of its forms – perhaps a customer card or an accounting transaction.
Because systems store information in diverse ways, actions are related to the underlying database involved. For example, one system might store external documents on a network file system, another in the cloud, and a third might embed document content in the database itself.
Typically, special programming is needed to support a given action for a particular database. Therefore, the set of available actions is pre-defined in Mercury.
Actions are currently available for the following system. See the reference for detailed information.
The Users tab controls settings for report access and the default report-list background-color. Note: Users can change their own report-list colors through the main Mercury window.
The Users tab is available for all report types.