Comments
Furthermore, when a user modifies team membership, the system should prompt the user—perhaps by asking if all team members should be added to each associated queue—rather than executing a default action without presenting alternatives. This approach would provide users with greater control and transparency throughout the process.
My team used this feature daily in NAV for planning our purchasing and production timelines; they still need the feature now that we are in BC.With our move to BC we stopped using a mod to manage available quantities and adopted base Item Availability across the organization. Now not just Supply Chain and Planning needs to see Item Availability but Sales, Customer Service, and even Warehousing all need to be on the same page with what is available, when it is available, and where (by Location).This feature would greatly improve visibility and collaboration when working with Item Availability and improve out adoption of the functionality.
Absolutely agree — this is a fantastic idea and something we really need! Bulk updating the Status Reason field would drastically improve efficiency, especially for teams managing a large number of segments. It’s a much-needed enhancement that would save time, reduce manual errors, and make the platform far more scalable and user-friendly. Hope to see this implemented soon!
This idea is strongly needed in today's global market. Currently, Microsoft Dynamics 365 Business Central does not support automated language translation for custom-developed features. All translations must be handled manually. This includes:Adding captions if they are missing during programming.Replacing hardcoded messages with labels to support localization.Adding tool tip captions. Below format is what Microsoft suggests For example:var MyLabel: Label 'This is a translated message.';begin Message(MyLabel);end;but most developers add Message('This is a translated message'). These are not handled during translation and becomes tedious work. This manual process becomes especially time-consuming and error-prone when deploying customizations across multiple countries or regions even if Microsoft standard development is followed(ex. if there're 50,000 customized fields that needs translation). A built-in automation tool from Microsoft to manage translations covering Multi-language, captions, tooltips, dialog boxes, and other UI elements would significantly streamline localization efforts and reduce development overhead.Such a feature is not just a convenience but a necessity for global deployments. It would greatly enhance productivity and ensure consistency in multilingual environments.