Skip to content

Commit f711ea3

Browse files
authored
Update simple-report.md
1 parent 48ef606 commit f711ea3

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

support/dynamics-365/finance/financial-reporting/simple-report.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
# required metadata
33

44
title: Troubleshoot report design and data issues
5-
description: Describes how to create a simple report to analyze some issues that occur in Microsoft Dynamics 365 Finance reports.
5+
description: Describes how to create a report to analyze data issues that can occur in Microsoft Dynamics 365 Finance reports.
66
author: aprilolson
77
ms.date: 01/29/2025
88

@@ -27,13 +27,13 @@ ms.custom: sap:Financial reporting and management reporter\Issues with report de
2727

2828
A practical way to troubleshoot report design or missing data issues effectively 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. In some cases, manually recreating a report or starting over with the design helps uncover design flaws or process bugs.
2929

30-
To help determine the cause of a data mismatch, some common areas to validate are:
31-
- Create a simple report to troubleshoot the issue.
30+
To troubleshoot report issues, confirm that following:
31+
- Create a minimal report to troubleshoot the issue.
3232
- Check that your data mart integration is current and healthy.
3333

3434

35-
## Create a simple report for troubleshooting
36-
To create a simple report to troubleshoot report issues, follow these steps:
35+
## Create a report for troubleshooting
36+
To create a report to troubleshoot report issues, follow these steps:
3737
1. Simplify the report as much as possible. The goal is to get to a single number.
3838
2. Remove any reporting tree and dimension set.
3939
3. Set the **Detail level** to **Financial**, **Account**, and **Transaction**.
@@ -47,8 +47,8 @@ To create a simple report to troubleshoot report issues, follow these steps:
4747
8. Verify the report is working as expected.
4848
9. Add one modification at a time if your issue includes specific design requirements.
4949
a. For example: currency filter, attribute filter, year-to-date, or beginning balances.
50-
10. If the issue still exists, contact support and provide the following:
51-
- Export .tdbx files of the simplified and original reports.
50+
10. If the issue still exists, contact support and provide the following information:
51+
- Export the .tdbx files of the simplified and original reports.
5252
- Screenshots of the simplified report build block designs including rows and columns.
5353
- Excel export of the report output.
5454
- Reporting parameters: **Company**, **Reporting date**, and **Report name**.
@@ -57,9 +57,9 @@ To create a simple report to troubleshoot report issues, follow these steps:
5757
### Check the data mart state
5858
To check the state of your data mart, follow these steps:
5959
1. In **Report designer**, go to **Tools** > **Integration status**.
60-
2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after you created your data. Usually, the General Ledger transactions are tracked to **Fact map**. Occasionally, due to system load and data volume, this can take longer. You may need to wait more than one hour for larger data changes to complete integration into data mart.
60+
2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after you created 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 may need to wait more than one hour for larger data changes to complete integration into data mart.
6161
3. To check more detailed statistics, go to **Tools** > **Reset data mart**. DO NOT reset the data mart.
62-
If there are transactions with six or more attempts, this could be *stuck* data due to integrity issues. Having amounts here doesn’t mean data is missing from your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
62+
If there are transactions with six or more attempts, there could be data integrity issues. Having amounts here doesn’t mean data is missing from your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
6363
4. If there are any **Misaligned main account** categories, reports based on account categories could report incorrect amounts.
6464

6565

0 commit comments

Comments
 (0)