on
RE:
This will be an extremely useful featureIn its absence, it would be very challenging to implement the custom invoice model
RE:
My customers needs this. Is there a cause, why it is still not possible?
RE:
I am sure this feature was working in AX2012 as we have used it extensively in previous implementations. It would be great to see it back.
RE:
Fully agree with the comments below — it's difficult to understand why kilometers are still not supported as a default unit of measure for mileage expenses, especially considering that over 90% of the world uses the metric system.As someone working on global D365FO implementations, we constantly need to build workarounds or customizations just to support basic regional needs like this — whether it's in Expense Management or Transportation Management (TMS), where miles are also still hardcoded in the standard mileage engine.If Microsoft wants Dynamics 365 to be a truly global solution, it’s essential to start addressing these long-standing requests. This idea has been here since 2019, yet still hasn’t moved forward.Please prioritize metric system support — it’s not a feature request, it’s a localization necessity.Elise De Brie
RE:
Resolved in release wave 1 2025
RE:
Even if they become separate docker specific scripts and whatever else we need to develop locally, I would be all for that!If not, they will have to give us more sandboxes and change how they impact a customer's storage allowance, but I would prefer to keep using docker locally
RE:
We definitely need this improvement. We have many PO's with multiple lines. We are Invoiced per line. Therefore having to manually remove the invoice from PO then add to the Posted PO.
RE:
For all the clients who should move soon from GP to BC, the fact that BC doesn't offer this (like in GP) is a stumbling block. The proposal of BC to put an ending period by user doesn't fit with the ending month process.
RE:
On the same note, Microsoft released a change to the phone number field to standardize it with the format "+ (Area Code)". However, after this change, the phone number field in our forms no longer matches the format of the other default fields. This inconsistency affects the user experience.
RE:
This is a critical limitation within the system and leads to performance issues when generating a large volume of invoices simultaneously. Microsoft should prioritize addressing this problem.