Comments
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.
I agree with this idea. Also it required to add functionality to track the inventory availability (counting ) by Attributes. It is very difficult to get the stock details by Attributes. If there is some enhancement added in Attribute side that will be really helpful. I have faced challenges when getting data from Shophify to synchronize in business central where inventory can not be counted based on attributes. Thanks
I have had multiple clients request the ability to have Standard Cost by Location and have had to implement various work arounds to address these needs. In order to support that would have to ensure that changes in standard costs as an item moves from one location to the other are handled.This would be huge feature for standard cost environments.