You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/finance/financial-reporting/simple-report.md
+34-26Lines changed: 34 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
# required metadata
3
3
4
-
title: Troubleshoot report design and data issues
5
-
description: Describes how to create a report to analyze data issues that can occur in Microsoft Dynamics 365 Finance reports.
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
6
author: aprilolson
7
-
ms.date: 01/29/2025
7
+
ms.date: 02/05/2025
8
8
9
9
# optional metadata
10
10
@@ -25,43 +25,51 @@ ms.custom: sap:Financial reporting and management reporter\Issues with report de
25
25
---
26
26
# Troubleshoot report design and data issues
27
27
28
-
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.
28
+
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.
29
29
30
-
To troubleshoot report issues, confirm that following:
31
-
- Check that your data mart integration is current and healthy.
32
-
- Create a minimal report to troubleshoot the issue.
30
+
To troubleshoot report issues, confirm that following:
31
+
32
+
- Check that your data mart integration is current and healthy.
33
+
- Create a minimal report to troubleshoot the issue.
34
+
35
+
## Check the data mart state
33
36
34
-
### Check the data mart state
35
37
To check the state of your data mart, follow these steps:
38
+
36
39
1. In **Report designer**, go to **Tools** > **Integration status**.
37
-
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.
38
-
3. To check more detailed statistics, go to **Tools** > **Reset data mart**. DO NOT reset the data mart.
39
-
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.
40
-
4. If there are any **Misaligned main account** categories, reports based on account categories could report incorrect amounts.
40
+
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 might need to wait more than one hour for larger data changes to complete integration into data mart.
41
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 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.
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 could report incorrect amounts.
42
47
43
48
## Create a report for troubleshooting
49
+
44
50
To create a report to troubleshoot report issues, follow these steps:
51
+
45
52
1. Simplify the report as much as possible. The goal is to get to a single number.
46
-
2. Remove any reporting tree and dimension set.
53
+
2. Remove any [reporting tree](/dynamics365/fin-ops-core/fin-ops/analytics/financial-reporting-tree-definitions) and dimension set.
47
54
3. Set the **Detail level** to **Financial**, **Account**, and **Transaction**.
48
-
4. Remove any other special options.
49
-
5. In the row definition, include a single row with a single account or dimension combination.
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.
50
58
- No wildcard or ranges.
51
59
- No modifiers or calculations to start.
52
-
6. In the column definition, include a single **DESC** and **FD** column for a specific period.
53
-
- Fiscal year: 2025 (specific year)
54
-
- Period: 11 (specific period)
55
-
- Periods covered: PERIODIC
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
56
65
- Remove all modifiers for the column.
57
-
8. This should display a report with a single cell of data.
58
-
9. Verify the report is working as expected.
59
-
10. Add one modification at a time if your issue includes specific design requirements. For example: currency filter, attribute filter, year-to-date, or beginning balances.
60
-
11. If the issue still exists, contact support and provide the following information:
61
-
- Export the .tdbx files of the simplified and original reports.
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. Add one modification at a time if your issue includes specific design requirements. For example, currency filter, attribute filter, year-to-date, or beginning balances.
70
+
10. If the issue still exists, contact Microsoft support and provide the following information:
71
+
-[Export the .tdbx files](/dynamics365/finance/general-ledger/view-financial-reports#export-a-financial-report) of the simplified and original reports.
62
72
- Screenshots of the simplified report build block designs including rows and columns.
63
73
- Excel export of the report output.
64
74
- Reporting parameters: **Company**, **Reporting date**, and **Report name**.
65
75
- Details about the incorrect amount and what the expected value is.
0 commit comments