I have a Flow where I have an action "Get items" (pagination turned on) to give me only a given set of revenue items, they must have a date lower than a given date (revenue date of Monday from last week) and in the path of the item it must have the word "Offen" (meaning "open"), because we have setup different folders on the list with different permissions (open folder the tenants have write access and in the normal folder they only have read access).
I noticed that the action/filter gives me back to many items. Altough I specify the correct last Monday date and use "lt" as an operator I also get items in the result output that have that exact same date.
To make things more clear, here an example from a histroy run log:
the evaulated filter query looks like this: (Datum lt datetime'2021-03-08T00:00:00.0000000Z') and (substringof('Offen',FileDirRef))
(2021-03-08 is a Monday, I want to close everything that is earlier than this date, not earlier and this date).
But in the output I find for example this entry:
{
"@odata.etag": "\"1\"",
"ItemInternalId": "120129",
"ID": 120129,
"Title": "Eintrag",
"Jahr": "2021",
"Kalenderwoche": "10",
"Datum": "2021-03-08",
"MieterReference": {
...
},
...
"{FilenameWithExtension}": "Eintrag",
"{Path}": "Lists/Umsatz/99999/Offen/",
"{FullPath}": "Lists/Umsatz/99999/Offen/120129_.000",
},
You see, the entry has a "Datum" value like this: "Datum": "2021-03-08"
So, why isn't it filtered out from the result? I checked if maybe I missinterpreting the OData "and" operator the wrong way, so that "and" means rather or (left part OR right part) but my results only contains item where "Offen" is part of the path (and I know it has items that don't have this in the path). So it looks that at least the right part of the filter is correctly working but I don't see why the date part is not working.
I guess it shouldn't be a timezone issue, since the query output looks like it correctly uses the UTC time.
By the way. "Datum" is a date field in the list of SharePoint Online and it is set to "date only".
Any ideas?
Solved! Go to Solution.
After fiddling around a bit more, it looks like this may be indeed some UTC/timezone issue. When I manually make the OData query for this item in my browser and have a look at the XML result I get the following values:
<content type="application/xml">
<m:properties>
...
<d:Datum m:type="Edm.DateTime">2021-03-07T23:00:00Z</d:Datum>
...
</m:properties>
</content>
So, I get it that when I, as a swiss user enter the 8th March of 2021 it is saved as 2021-03-07T23:00:00Z, because SPO works with UTC, and SharePoint automatically converts the time back and forth.
OK, so I guess I have to use the "convertToUtc()" function to convert my "Last Monday date" value to UTC and then use this result for my filter.
(But still strange that the Flow history output shows me the date as "2021-03-08", why is it converted there?)
I will try this out and let you know.
After fiddling around a bit more, it looks like this may be indeed some UTC/timezone issue. When I manually make the OData query for this item in my browser and have a look at the XML result I get the following values:
<content type="application/xml">
<m:properties>
...
<d:Datum m:type="Edm.DateTime">2021-03-07T23:00:00Z</d:Datum>
...
</m:properties>
</content>
So, I get it that when I, as a swiss user enter the 8th March of 2021 it is saved as 2021-03-07T23:00:00Z, because SPO works with UTC, and SharePoint automatically converts the time back and forth.
OK, so I guess I have to use the "convertToUtc()" function to convert my "Last Monday date" value to UTC and then use this result for my filter.
(But still strange that the Flow history output shows me the date as "2021-03-08", why is it converted there?)
I will try this out and let you know.
Hi @TheShihan,
Any DateTime type of columns we create within SharePoint, are stored in UTC format internally. Any custom implementation which accesses the DateTime values programatically, will get the DateTime values returned in UTC as well. So, when a SPFx webpart tries to read list items with DateTime field values, using PnPjs, REST API or any other supported models, the DateTime values are always returned in UTC format. Due to this we might be seeing appropriate DateTime values within SPFx webparts.
Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
To give an update, I was indeed able to solve the issue by converting the date for my OData filter from my local timezone (timezone setup in the regional settings of SharePoint) to UTC using the "Convert To Timezone" action.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages