Table Alias Conversion

Reports created prior to 8.0.14 did not use the Table Alias Mapping system but instead directly reference the actual qualified table names. Reports/table lookups generated from version 8.0.14 onwards will automatically incorporate table aliases. However, for reports created before this version, there is a straightforward method to convert them for table alias usage.

The conversion process will attempt to convert all of the report's table joins and table lookup calculations to use table aliases. For example, an old report might have a column reference [Prod].[TestTable].[ColA]. After conversion, this reference will instead be [TestTable].[ColA]. If the external connection did not already contain an alias mapping for [Prod].[TestTable], a mapping will be created (e.g. [Prod].[TestTable] --> [TestTable]).

If the table name is already used by the connection but mapped to a different qualified table name (ex. [Dev].[TestTable] --> [TestTable]), a new unique alias will be added (ex. [Prod].[TestTable] --> [Prod_TestTable]). The updated column reference in this example would then be [Prod_TestTable].[ColA].

Note

Reports that are not converted will still continue to work and can be modified like normal. However, if the external table that the report relies on changes in the future it will require manual intervention to fix.

Converting Reports and Table Lookups

Upon conversion, the report will open in a new tab to provide users with the option to close it without saving, preserving the original report. To convert a report join or table lookup calculations, please follow the steps below:

  1. Open desired report
  2. Click on Design > Table Join
  3. Click on Advanced Options in the top right corner
  4. Click on Convert to use simple table alias
  5. Verify that the report is still working as intended

Considerations Before Converting

While we recommend converting reports to utilize table aliases, it is essential to consider a few factors before proceeding. It is important to understand that the column references of a report are often used by other objects to connect or 'bind' to the report. For example, a dashboard may have a chart that is bound to a report's column. If the report's column reference changes, the dashboard will no longer be able to bind to the report. Therefore, it is crucial to understand the impact of converting a report before proceeding.

Systems that can bind to a report's column reference include:

  • Dashboards
  • ProReports
  • Burst Calculations

In cases where the report has viewers (dashboards or ProReports) referencing the report being converted, users will receive a warning before initiating the conversion. The converted report will open in a new tab with a unique name to ensure that viewers remain unaffected. After testing the converted report, users should go into each viewer that is linked to the old report and then change it to the newly converted report. Since the report was opened with a new unique name, this will give users ample time to make necessary adjustments and address any potential issues.

There are no warning dialogs for burst dependencies. You will want to use the Burst/Drilldown Cross Reference report to identify any burst dependencies. If there are any burst dependencies, you will want to test and update the burst calculation after the conversion if the burst call referenced any of the changed columns.

Remarks

While the report/table lookup may already be using table aliases, if it is not using the most simplified version for that table then the option to convert to use simple table alias will show up under the advanced options.