0
Category:
STATUS DETAILS

Comments

This is really important for maintenance of best practices while implementing MSM. You don't want to test out and approve your configurations in a sandbox environment and then recreate them manually in a Production environment. It can introduce errors.

Category:

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

Category:

This is similar to another idea https://experience.dynamics.com/ideas/idea/?ideaid=50e51819-afc6-ea11-bf21-0003ff68dcc1

Category:

This is similar to another idea https://experience.dynamics.com/ideas/idea/?ideaid=50e51819-afc6-ea11-bf21-0003ff68dcc1

Category:

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.

Category:

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.

Category:

I completely agree. MR has functionality that core BC financial reports does not. The BC reports need users to polish the report when exported as well as dynamic dates need to be fixed. MR has this functionality. For smaller clients that already user MR for GP, migration of those reports would be simple

Category:

This has been a very common request for every customer I have worked with so far. It's high time PG should start looking into solution options for this requirement.

Category:

Fully agree. We can't manage what we can't measure. Excluding service revenue and profitability from core reports gives us an incomplete picture of our business. This should be a high-priority fix to make D365 a true single source of truth for sales performance.

Category:

most of our customers using planning worksheet we have to change to listpage because listpage can save the filters... but it would be so nice that worksheet also could same filters... so YES please :)

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500