Dynamic Reports Best Practices

Article summary

Did you find this summary helpful?

Thank you for your feedback

The following best practices and tips are recommended to optimize functionality, reduce processing time, and streamline report setup and design.

Scenario should be on the Page axis. For example, if the column set has current year, prior year and budget, then the Actual scenario should be on the Page axis and budget on the Column axis.
If one dimension (not the one that the row set or column set is defined on) is on many of the rows or columns, it should be moved to the page level and not mapped.
If a Profit and Loss report is created, it will default to MTD (month to date) so there is no need to map on the column.
If a Balance Sheet is created, it will default to YTD (year to date) so no need to map on the column.
If there are several chart strings that are to be combined on one line, it is better to list each of the accounts on a separate line, hide those lines, and then combine with an Excel formula in a row set.

Use the Save As/Copy options to quickly create reports with similar data structures.

Use Report Sets as templates to create formatted and strategic reports.

Design reports using dimensions that support operational reporting.

Before running a report, verify that the Lock Data settings match the reporting period you intend to view.

To verify the Lock Data settings, do the following:

Apply security access to control user access to a report.
To access report security, do the following:
1. Navigate to Reports.
2. From the File Cabinet, select a report for which you want to define security access.
3. From the Share drop-down, click Share Access. The Share Reports window appears.
4. Configure the required accesses for users, and then click Share.

Note:
This Share Access feature is enabled by default for all new and existing customers.

Use the Export to PDF option for high-quality PDFs. Share the report with others via email.
Use the Send Email option to share the report as Excel via email.

When using large amounts of content in the header or footer cells, adjust the margins in print settings so that the content fits the page.
When exporting a dynamic report to PDF, remove underlines and double underlines under the page number, as this formatting is not supported.
The alignment of an image in a header/footer cell is applied only when you move out of the cell.
Page number must be used in the 2nd or 3rd column of the first header row. If page number is applied in any other cells, you might not get the desired result in PDF or Excel outputs.
Use one image per cell. Image should not be used with text.

Avoid using drill-down when the following options are selected:

Ensure that only required member selections are made on each axis.
Organize segment hierarchies intuitively to get best results on drill-down. Drill-down works well with hierarchies on multiple levels, but is not functional when you have a flat hierarchy (for example, 300 members under a single node).
Ensure the following while data input during simultaneous hierarchy or report maintenance.
- Suppose a user enters data in a report while hierarchy or report maintenance is taking place, when the data is saved. In that case, it will be written into the intersection that reflects the latest maintenance updates, not necessarily what was displayed in the report.
- Example 1: A user inputs sales data for Region 3 while an Admin re-sorts the regions numerically (Region 1, Region 2, Region 3). Upon saving, the inputs are written to Region 2 instead of Region 3.
- Example 2: A user edits data in a web report while a Power User simultaneously changes the report structure in SpotlightXL (e.g., switching rows). Once the data is saved, it is written to the new row intersection, not the one currently displayed.
This issue occurs when maintenance impacts a row or intersection that has not been refreshed. To avoid data shifting, refresh reports before saving inputs when structural updates may be occurring.

Was this article helpful?

Table of contents