Comments
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.
Relates to LCS ISSUE 756782 https://fix.eu.lcs.dynamics.com/Issue/Details/1429?bugId=756782&dbType=3&qc=50bf9570dd9e20dc32d9bf607fb4d3adb6f63d9be24571a522462b55a7acb131As this data is the basis for INTRASTAT-Reporting which is a regulatory requirement at least within the EU, for me this should be fixed in the core for all, rather than individually in each instance.