|
| 1 | +--- |
| 2 | +# required metadata |
| 3 | + |
| 4 | +title: Troubleshoot Report Design and Data Issues |
| 5 | +description: Describes how to create a report to analyze data issues that occur in Microsoft Dynamics 365 Finance reports. |
| 6 | +author: aprilolson |
| 7 | +ms.date: 02/17/2025 |
| 8 | + |
| 9 | +# optional metadata |
| 10 | + |
| 11 | +ms.search.form: FinancialReports |
| 12 | +# ROBOTS: |
| 13 | +audience: Application User |
| 14 | +# ms.devlang: |
| 15 | +ms.reviewer: twheeloc |
| 16 | +# ms.tgt_pltfrm: |
| 17 | +ms.collection: get-started |
| 18 | +ms.assetid: 3eae6dc3-ee06-4b6d-9e7d-1ee2c3b10339 |
| 19 | +ms.search.region: Global |
| 20 | +# ms.search.industry: |
| 21 | +ms.author: aolson |
| 22 | +ms.search.validFrom: 2016-02-28 |
| 23 | +ms.dyn365.ops.version: AX 7.0.0 |
| 24 | +ms.custom: sap:Financial reporting and management reporter\Issues with report designer |
| 25 | +--- |
| 26 | +# Troubleshoot report design and data issues |
| 27 | + |
| 28 | +A practical way to troubleshoot design or missing data issues in [financial reporting](/dynamics365/fin-ops-core/fin-ops/analytics/financial-reporting-intro) is to simplify the process and control variables. Focusing on a specific scope is often more manageable than diagnosing an entire report. Start by creating the smallest possible reproduction of the issue and make changes one at a time to help isolate the problem. In some cases, manually recreating a report or starting over with the design can help uncover design flaws or process bugs. |
| 29 | + |
| 30 | +To troubleshoot report issues: |
| 31 | + |
| 32 | +- [Check that your data mart integration is current and healthy.](#check-the-data-mart-state) |
| 33 | +- [Create a minimal report.](#create-a-minimal-report) |
| 34 | + |
| 35 | +## Check the data mart state |
| 36 | + |
| 37 | +To check the state of your data mart, follow these steps: |
| 38 | + |
| 39 | +1. In **Report designer**, go to **Tools** > **Integration status**. |
| 40 | +2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after the creation of your data. Usually, the General Ledger transactions are tracked to **Fact map**. Occasionally, due to system load and data volume, data mart integration can take longer. You might need to wait more than one hour for larger data changes to complete integration into data mart. |
| 41 | + |
| 42 | +3. To check more detailed statistics, go to **Tools** > **Reset data mart**, but don't reset the data mart. |
| 43 | + |
| 44 | + If there are transactions with six or more attempts, there might be data integrity issues. It doesn't mean data is missing from your report, but it can be a source of missing data. Work with [Microsoft support](/power-platform/admin/get-help-support) to determine the cause of the stuck data. |
| 45 | + |
| 46 | +4. If there are [Misaligned main account categories](/dynamics365/fin-ops-core/dev-itpro/analytics/reset-financial-reporting-datamart-after-restore#misaligned-main-account-categories), reports based on account categories might report incorrect amounts. |
| 47 | + |
| 48 | +## Create a minimal report |
| 49 | + |
| 50 | +To create a minimal report to troubleshoot report issues, follow these steps: |
| 51 | + |
| 52 | +1. Simplify the report as much as possible. The goal is to get to a single number. |
| 53 | +2. Remove any [reporting tree](/dynamics365/fin-ops-core/fin-ops/analytics/financial-reporting-tree-definitions) and dimension set. |
| 54 | +3. Set the **Detail level** to **Financial**, **Account**, and **Transaction**. For more information, see [Report definitions](/dynamics365/fin-ops-core/fin-ops/analytics/design-financial-report-definitions). |
| 55 | +4. Remove other special options. |
| 56 | + |
| 57 | +5. In the [row definition](/dynamics365/fin-ops-core/fin-ops/analytics/row-definitions-financial-reporting), include a single row with a single account or dimension combination. |
| 58 | + - No wildcard or ranges. |
| 59 | + - No modifiers or calculations to start. |
| 60 | + |
| 61 | +6. In the [column definition](/dynamics365/fin-ops-core/fin-ops/analytics/column-definitions-financial-reports), include a single **DESC** and **FD** column for a specific period. |
| 62 | + - **Fiscal Year**: 2025 (specific year) |
| 63 | + - **Period**: 11 (specific period) |
| 64 | + - **Periods Covered**: PERIODIC |
| 65 | + - Remove all modifiers for the column. |
| 66 | + |
| 67 | +7. This should display a report with a single cell of data. |
| 68 | +8. Verify the report is working as expected. |
| 69 | +9. If your issue includes specific design requirements, such as currency filter, attribute filter, year-to-date, or beginning balances, add these modifications one at a time. |
| 70 | +10. If the issue still exists, contact [Microsoft support](/power-platform/admin/get-help-support) and provide the following information: |
| 71 | + - [The .tdbx exported files](/dynamics365/finance/general-ledger/view-financial-reports#export-a-financial-report) of the simplified and original reports. |
| 72 | + - Screenshots of the simplified report build block designs including rows and columns. |
| 73 | + - Excel export of the report output. |
| 74 | + - Reporting parameters: **Company**, **Reporting date**, and **Report name**. |
| 75 | + - Details about the incorrect amount and what the expected value is. |
| 76 | + |
| 77 | +## More information |
| 78 | + |
| 79 | +[Best practices for optimizing financial reports](/dynamics365/finance/general-ledger/fin-reports-best) |
0 commit comments