Skip to content

Commit feb00ab

Browse files
authored
Revising per issue feedback.
1 parent 5009d87 commit feb00ab

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

powerapps-docs/maker/model-driven-apps/reporting-considerations.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ description: Learn about what the considerations are when you use reporting in m
44
ms.custom:
55
ms.date: 09/27/2019
66
ms.reviewer:
7-
87
ms.suite:
98
ms.tgt_pltfrm:
109
ms.topic: conceptual
@@ -42,7 +41,7 @@ As the volume of data held in the app's database continues to grow it becomes mo
4241

4342
## Reporting infrastructure
4443

45-
In an environment, the reporting infrastructure is shared and separate from the database. In this architecture, although customers share the resources required to run the report, each report runs against the customers’ individual database instance. Additionally, users can run as many reports as they need whenever they want to run them to meet business goals. We do not place time restrictions on reports.
44+
In an environment, the reporting infrastructure is shared and separate from the database. In this architecture, although customers share the resources required to run the report, each report runs against the customers’ individual database instance. Additionally, users can run as many reports as they need whenever they want to run them to meet business goals.
4645

4746
The reporting capabilities built in to Microsoft Dataverse are designed to let users run reports on datasets that span shorter periods of time. Considering this, note the following fixed settings:
4847

@@ -107,4 +106,4 @@ If users must run reports that exceed these settings, we recommend that you revi
107106

108107

109108

110-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
109+
[!INCLUDE[footer-include](../../includes/footer-banner.md)]

0 commit comments

Comments
 (0)