D365 for Talent uses datetime registrations at all levels (dd/mm/yyyy hh:mm:ss), including: 1) Worker position assignment 2) Employment 3) Term of employment 4) Position effective date This leads to a series of challenges: 1) D365 FT does not always default the timestamp correctly in different timezones. 2) End-users need to pay explicit attention to these timestamps. 3) Becasue of time conversion towards GMT, this leads to challenges when interfacing to other systems. For example 03/05/2019 00:00:00, becomes 02/05/2019 23:00:00 in GMT +1. This leads to extra conversion work on the interface and makes the solution more difficult to scale up, when faced with a customer active in a wide range of timezones. When the datetime behavior would be replaced by "date only" behavior, these issues will be solved. This is imo a best practice among competing HRIS solutions. Vote for this idea and make D365FT ready for the enterprise market.
Comments
This is a must have - I actually came here to make this suggestion - no company cares for the time someone starts, its always going to be 00:00 - The date should not change when the clocks change, if I start on 1st of Jan, when the clocks change it changes to me starting on 31st Dec - really really silly and messes with reporting.
Category: Personnel management
This would really benefit all our customers.Is there any progress on this topic?
Category: Personnel management
A real struggle- we work across the globe and struggle now with workforce reports based on a snapshot date and also interfaces, or power apps or flows!Could add the position details to the list above!
Category: Personnel management
Must have, working with datetime fields should at least be optional. Has been a struggle for user input, data migration, interfaces and reporting on each project I've been involved with.
Category: Personnel management
Must have!!!
Category: Personnel management
Must have !!! Do we have a status on this?
Category: Personnel management
Must have for us! Would be great to have this implemented
Category: Personnel management
Must have!
Category: Personnel management
a really essential point which must be implemented!
Category: Personnel management
Absolutely a must, can only confirm what has been stated above! Having the timestamp creates issues with any kind of integration (payroll, power platform, etc). For organizations working on different time zones - hence almost any organization with multiple subsidiaries - it creates confusion, with employees having to think in GMT terms when entering dates where the time does not add value.
Category: Personnel management
Administrator on 2/4/2025 6:31:08 AM
Thank you for your suggestion. We’re considering this functionality for a future release. This posting is provided “as is” with no warranties, and confers no rights.