Comments
Dear Johan,I understand your comment, but this won't work when you run a batch to bring the production order status from reported as finished to ended. After the batch someone still has to proces these production orders as you mentioned.For me STD cost items are super simple.If there is no good output quantity reported then all the reported cost (WIP) are going to the variance accounts.Please reconsider your decision so that we can make the ending of production orders fully automated.Thanks,Niels
Hello,However, the link they provided doesn't specify whether the functionality will be available for the on-premise version in October 2026.I've seen that the Verifactu module is already included in version 27 of the SaaS version, which was released in the spring.But I haven't seen any news from Microsoft indicating that it will be available for the on-premise version without needing third-party tools like b2brouter—that is, that it will be natively integrated, like the SII (Spanish Tax Agency).Regards,
In a multilingual ERP system, Item Charges should support translations instead of forcing customers to create separate Item Charges for each language.Creating duplicate Item Charges only to maintain different descriptions leads to unnecessary master data growth, increased maintenance effort, and a higher risk of inconsistent configurations.An Item Charge is a business object, not a language-specific object. The description shown on documents should be determined by the document language, while the Item Charge itself should exist only once.Translation support would improve data quality, simplify administration, and align Item Charges with other Business Central entities that already support multilingual descriptions.This is a small enhancement with significant benefits for every international Business Central customer.
Also include: Multi-select receipts when uploading unattached receipts in the Expense mobile appCurrently, the Dynamics 365 Expense mobile app only allows users to upload unattached receipts one at a time. Each receipt requires a separate upload flow, which makes the process slow and repetitive. This is a significant pain point in common scenarios:After a business trip, users typically return with many receipts (taxi, meals, parking, hotel) and want to capture them all in one sessionUsers who photograph receipts throughout the month and upload them in batches must repeat the same upload steps for every single imageFrequent travelers with high expense volumes lose the efficiency benefit that mobile receipt capture is meant to provide Today, the workaround is either to upload receipts one by one in the app, or to switch to the web client for bulk handling. Both options add friction and discourage users from capturing receipts promptly, which in turn increases the risk of lost receipts and delayed expense reporting. Standard mobile OS capabilities (photo picker multi-select) already support selecting multiple images in one action, so the interaction pattern is well established and familiar to users. Suggestion: Allow users to select and upload multiple receipts in a single action when adding unattached receipts in the Expense mobile app, so a stack of receipts can be captured in one session instead of one upload flow per receipt.
Strongly agree.I have worked for over 10 years in an accounting services company managing around 100 customer environments across NAV 4.0, NAV 5.0, NAV 2009, NAV 13, 15, 16, 17, 18 and BC14 On-Premises.In my experience, those older on-premises versions have not caused anywhere near the same amount of operational disruption as the current online update model.The challenge is that accounting firms and service providers often manage large numbers of customers. When an update introduces a regression, the impact is multiplied across dozens or even hundreds of companies, creating a significant support burden with little warning and no additional resources.We need more control over update scheduling, better phased rollouts, and the ability to keep sandboxes ahead of production for a meaningful validation period.Not every update needs to land in the middle of the summer vacation season.