Comments
I believe we have a similar need / requestOur security role is setup with 'parent-child' access for journeys. However the Analytics dashboard (aggregate cross-journey analytics) simply seem to display the analytics organization wide .. not just as aggregate cross-journey (for journeys users have access to).Users neither have any option to filter their own (aggregate cross-journey) statistics in here .. other than selecting the journeys by name (in the entire list of all journeys) so that makes this dashboard inconvenient or even useless as such.Is this already planned? Any update on the ETA or planning?
we need this for our production environment. Once we purchase dataverse storage, we don't want the space to be utilised by other environment belonging to other country team or by our citizen developers. We don't have centralised admin and we cannot enforce limit on other countries environment
With clients having to move to new platforms from GP, it is beneficial to MS to keep these clients in the MS world. To do so requires clients to maintain the features they have in GP that they know and love along with giving them greater flexibility in a new system. Since users currently have the functionality to close out statistical accounts in GP, these would be a good selling feature and beneficial to clients to have this option in BC. Currently the options available to them are cumbersome or expensive.
This functionality is essential for organizations using statistical accounts in Business Central. Dynamics GP has a built-in year-end reset for statistical accounts that clears balances while preserving historical data—a feature that many businesses rely on for accurate reporting and smooth year-end processes. Business Central currently lacks this capability, forcing users into manual workarounds like configuration packages or statistical journals, which are time-consuming and error-prone.While there is a ‘Reverse Entries’ option in the Statistical Ledger Entries table, it is not ideal because it posts reversals using the original posting dates. This means balances do not reset cleanly at year-end, and reporting across fiscal periods becomes confusing.Adding a proper year-end reset feature would:Streamline closing processes and reduce manual effortMaintain audit integrity by preserving historical data without deleting entriesImprove adoption for GP customers moving to BC by retaining a critical capabilityThis is not just a convenience—it’s a fundamental requirement for accurate operational and statistical reporting. Please prioritize this enhancement to bring Business Central in line with GP’s robust functionality.