Last week I was creating a solution using Power Platform, the requirements were really simple “I would like to send a set of documents for approval”, “I want to make it user friendly for the users”.
After making some tests with Document Sets (which I personally not that familiar) I decided to give it a try to avoid sending multiple approval requests for documents that are related to the same topic. The architecture of the solution is simple, I created a SharePoint list to store the approval request metadata, a SharePoint library to store all the documents to be approved and then I created a second library with Document Sets to have the approved documents. Then I built a Power Apps to give the nice user-friendly interface and Power Automate cloud flows to build the business logic and automation. The process finishes with a cloud flow “Approved item handler” which is triggered when a SharePoint item is modified with the status “Approved”, this flow basically creates the document set in the target library and passes the metadata input from the approval request, including a date column.
I realized that the trigger had the date-only column as “2026-06-22”, and I was passing exactly that same value in the “Create a document set” action, however, in SharePoint instead of seeing the date “22/06/2026” I was seeing “21/06/2026” how is this possible?
I made some investigations using the SharePoint Rest API and the result was the following:
Source List:
"2026-06-22T22:00:00.00Z"
Target Library:
"2026-06-22T20:00:00.00Z"
My timezone is Central European Timezone (UTC+2), after making some reflections I have the impression that SharePoint was actually converting the time twice. I tried different approaches such as converting the time to UTC prior sending or sending a fixed time, none of them worked. However, I was able to fix it by just using a “Update file properties” action after creating the document set, and even though I was sending the same value “2026-06-22” it works correctly.