Hi,
I am facing inconsistency in date values while pulling data from a Dataverse table using a virtual table.
- The field in the Dataverse table is defined as timezone-independent (so it should only return the date value).
- For example:
- If the datetime stored in Dataverse is 21/09/2025 11:59:59 AM, the virtual table returns the correct date: 21/09/2025.
- But if the datetime stored in Dataverse is 21/09/2025 12:00:00 PM, the virtual table returns 22/09/2025 (the date is rounded up by 1 day).
After testing multiple cases, I observed:
- If the time part is in AM, the returned date is consistent.
- If the time part is in PM, the returned date is shifted to the next day.
- There is no impact of Time-Zone Configuration.
I cannot change the field property in Dataverse because this table is synced from F&O HR via dual-write.
My questions is:
- Is this rounding behavior (AM = same day, PM = next day) expected when Dataverse converts a datetime field to date in a virtual table, or is this a bug/limitation?
Thanks in advance for clarification.