Handling British Summer time when querying SharePoint from Power Automate

-

This also applies to other TimeZones.

When you query SharePoint in Power Automate using steps like "Get Items" the raw information that is returned when you are working with dates and currently inside British Summer Time will be out by an hour.

Below I've created a step which runs Get Items and I add a compose to check the Created date:


Going into SharePoint you can see the date time returned is an hour out (I'm currently inside British Summer Time and my laptops date/time is set as such).


Whenever you are handling dates from SharePoint in Power Automate you have to remember that the original value stored in SharePoint for date/time is the UTC value. Depending on your regional settings the value is converted for you when it's rendered.

Fear not! Power Automate has conversions, here's one way:


In the example above I'm taking the source Created date/time which is in UTC and converting it to my location - Dublin, Edinburgh, Lisbon, London. The expected Created time is returned:


Another method (as more of a one liner) which you can use when setting a field is included below.
Note: ("items('Apply_to_each)'?['Created'] is the Created date/time from SharePoint):

convertTimeZone( items('Apply_to_each')?['Created'] ,'GMT Standard Time', 'UTC','yyyy-MM-ddTHH:mm:ss')



This also counts when you are querying SharePoint date/time fields! So definitely store a converted date in UTC format if you are then using it in "Get Items" with an odata query. 

E.g. if you make up your own specific time like 25/06/2023 @ 15:00BST you'll want to convert this to UTC first by doing the opposite of the above.

Hope it helps!

Comments

Post a Comment

Popular posts from this blog

Use Power Automate to create a Document Set – The easy way!

-
Image
NOTE: This makes a “pseudo” document set, use the VTI bin method to create a full blown document set, however perhaps some of the steps could be useful to you. I’ve recently been working with improving some workflows which use Document Sets and stumbled into a problem. Online when you search for “Document Sets using Power Automate” you get posts such as:  https://karinebosch.wordpress.com/2018/11/08/microsoft-flow-create-a-document-set/ https://knowhere365.space/microsoft-flow-sharepoint-document-set-creation/ Now these posts have helped a lot of people but there is one drawback to them and most of the others I can find online. They rely on the use of _vti_bin (sometimes referred to as SP 2010 REST API) If you don’t know much about the history of VTI go check this out: https://www.spjeff.com/2009/03/13/history-of-_vti_bin/ It’s pretty vintage now. The customer I’ve been working with has a handful of SharePoint 2010 workflows we discovered using the SharePoint Modernisation Scanner  
Read more

Power Automate - Get SharePoint items using Created By/Modified By

-
Image
Recently I had an interesting request where someone was trying to filter items based on the Created By field in SharePoint using Power Automate. I thought, that should be pretty straight forward, make a claim or something similar and I headed to Google. Surprisingly there's not actually that many hits and it took quite a bit of digging. The answer once you realise is pretty straight forward. SharePoint holds a hidden(ish) list, the "User Information List" you can view it by adding the following to a Site Collections URL:  /_catalogs/users/simple.aspx This list holds all the "Ensured Users" on the site - you can google that one if you want to find out more. It also holds the information on which you can use in the filters for People Fields. Here are all the useful filters you can use: "ItemInternalId":"11", "ID":11, "Title":"Martin Pyman", "Name":"i:0#.f|membership|martin@marnotechnology.com",
Read more