Comments
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
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.
I believe this could be achieved by going to Feature management, and enabling the "Decimals for rounding precision in leave and absence module" feature? This will of course impact the entire leave and absence module for the given legal entity including the amount in time off requests. You can search for the Learn: Dynamics 365: Dynamics 365 Human Resources page "Configure the number of decimal places in Leave and absence" for more details.