Return to Answer

We encountered similar “strange” results with an external application using search queries to retrieve document information. Your intuition about “UTC” was correct. When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For every column containing a date (timestamp) value, a second column is created with the same name but with a “.” appended to it. The second column stores the UTC value, while the first one stores the “ConvertedFromUTCtoLocalTimeZone” value. For example:

ColumnName = LocalTime.Value
ColumnName. = utcTime.value
'''

For more details, y[ou can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax][1].

Additionally, you might find the following resources helpful:

- [How to work with SharePoint datetime localization/timezones][1]: This article provides an in-depth look at how SharePoint handles date and time localization.
- [SharePoint UTC to Local time][2]: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.


  [1]: https://julieturner.net/post/sharepoint-datetime/
  [2]: https://community.fabric.microsoft.com/t5/Desktop/Sharepoint-UTC-to-Local-time/td-p/1736608

We encountered similar “strange” results with an external application using search queries to retrieve document information. Your intuition about “UTC” was correct. When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For every column containing a date (timestamp) value, a second column is created with the same name but with a “.” appended to it. The second column stores the UTC value, while the first one stores the “ConvertedFromUTCtoLocalTimeZone” value. For example:

['ColumnName']  = LocalTime.Value

['ColumnName.'] = UtcTime.value

For more details, you can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax.

Additionally, you might find the following resources helpful:

• How to work with SharePoint datetime localization/timezones: This article provides an in-depth look at how SharePoint handles date and time localization.
• SharePoint UTC to Local time: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.

We encountered similar “strange” results with an external application using search queries to retrieve document information. Your intuition about “UTC” was correct. When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For every column containing a date (timestamp) value, a second column is created with the same name but with a “.” appended to it. The second column stores the UTC value, while the first one stores the “ConvertedFromUTCtoLocalTimeZone” value. For example, ColumnName = LocalTime.Value and ColumnName. = utcTime.value.

For more details, you can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax.

Additionally, you might find the following resources helpful:

• How to work with SharePoint datetime localization/timezones: This article provides an in-depth look at how SharePoint handles date and time localization.
• SharePoint UTC to Local time: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.

We encountered similar “strange” results with an external application using search queries to retrieve document information. Your intuition about “UTC” was correct. When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For every column containing a date (timestamp) value, a second column is created with the same name but with a “.” appended to it. The second column stores the UTC value, while the first one stores the “ConvertedFromUTCtoLocalTimeZone” value. For example:

ColumnName = LocalTime.Value
ColumnName. = utcTime.value
'''

For more details, y[ou can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax][1].

Additionally, you might find the following resources helpful:

- [How to work with SharePoint datetime localization/timezones][1]: This article provides an in-depth look at how SharePoint handles date and time localization.
- [SharePoint UTC to Local time][2]: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.


  [1]: https://julieturner.net/post/sharepoint-datetime/
  [2]: https://community.fabric.microsoft.com/t5/Desktop/Sharepoint-UTC-to-Local-time/td-p/1736608

When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For more details, you can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax.

Additionally, you might find the following resources helpful:

• How to work with SharePoint datetime localization/timezones: This article provides an in-depth look at how SharePoint handles date and time localization.
• SharePoint UTC to Local time: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.

We encountered similar “strange” results with an external application using search queries to retrieve document information. Your intuition about “UTC” was correct. When a user picks a date and time, SharePoint saves it in UTC. When displayed, the system adjusts the time according to regional settings. The main distinction is that, unlike the consistent global date, the time part in the DateTime columns changes with different time zones.

For every column containing a date (timestamp) value, a second column is created with the same name but with a “.” appended to it. The second column stores the UTC value, while the first one stores the “ConvertedFromUTCtoLocalTimeZone” value. For example, ColumnName = LocalTime.Value and ColumnName. = utcTime.value.

For more details, you can refer to the Microsoft documentation on Keyword Query Language (KQL) syntax.

Additionally, you might find the following resources helpful:

• How to work with SharePoint datetime localization/timezones: This article provides an in-depth look at how SharePoint handles date and time localization.
• SharePoint UTC to Local time: A community discussion on converting UTC to local time in SharePoint.

These resources should give you a comprehensive understanding of how SharePoint manages date and time values across different time zones.