cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Using ODATA Filter Query on Get Items to Compare SharePoint List Date & Excel Date

Hello, first, thank you for looking into this issue, I appreciate you and your time.

I have an automated flow that triggers when a new excel file has been created in one of my SharePoint Libraries.  The flow creates a table in the excel file and then does an 'Apply_to_each' Get Items from my SharePoint List (Named: Shipping List).  I have an ODATA Filter Query that needs to compare Job Number and Due Date fields between the excel file and SharePoint List.  Those fields are used because they'll never be replicated.

 

This is to determine if Power Automate must create a new SharePoint list item or update an existing one.  I keep getting the following error:

Krickner_2-1679503531954.png

"Title" is my SharePoint column ID for "Job Number", the "200164-25" is just one example of a job number.  "Field_4"is Due Date.

 

 

I believe the issue is due to the date format, as it's probably coming in from the "List rows present in a table" in one format, while Get Items from the SharePoint list is in another format.  I don't know how to resolve this issue. (See Flow Below)


Krickner_1-1679503750379.png

 

 

 

Krickner_1-1679503448912.png

 

______________________________________________________________

 

Here is the formula I'm using to attempt to fix the issue, however, even without manipulating the date, it did not work.  Still, every ODATA filter query fails to find a match.

 

Krickner_0-1679504882991.png

----------------------------------------------------------------------------------------------------------------------------------

 

Krickner_0-1679504300716.png

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

@Sundeep_Malik, I finally got it to work, and I really appreciate your help on this one.  Oddly enough, I returned to the original flow and made one adjustment.  When formatting the date on the ODATA filter, I had to use hyphens "-" instead of forward slashes "/", and I also had to use the format "MM-dd-yyyy."  I'm posting the entire flow so that others can benefit should they need a flow like this. 

  1. The flow waits for an excel sheet to upload to a specific SharePoint library, which triggers the flow.
  2. Creates an excel table within the excel sheet with existing data.
  3. Gets items from a SharePoint list and compares the Excel table to SharePoint items.
  4. If an item already exists in the SharePoint list, the flow updates the SharePoint list item.
  5. The flow creates a new SharePoint list item if the item does not exist.

This flow also uses a document upload status field to let users know when the flow has been completed.  You must delete this logic if you do not want to create a custom document upload status field in your SharePoint library.

Krickner_1-1679918583915.png

Krickner_3-1679919084198.png

Krickner_4-1679919270391.png

Krickner_6-1679919600852.png

Krickner_7-1679920281628.png

Krickner_8-1679920646108.png

Krickner_10-1679920951875.png

 

 

 

 

 

 

 

View solution in original post

19 REPLIES 19
Sundeep_Malik
Multi Super User
Multi Super User

Hey @Krickner 

 

Do the condition like this:

 

(Title eq 'JobNumber') and (field_4 eq 'formatdatetimeexpression')

 

 

I'm going to try this now @Sundeep_Malik .  I'll update you in a few.  thank you : )

@Sundeep_Malik the same error occurred.  My instinct is telling me it has to do with date formatting, but I don't know how to see which date format the SharePoint list is using.  I set the "list rows present in a table (excel)" format to MM/dd/yyyy.  

I also tried changing the "formatdate" to be "MM/dd/yyyy" which excludes the time.  My SharePoint List column is not set up to display time (see below).  I figured it would be a long shot as I'm pretty sure it keeps that data on the backend and uses it when importing into Power Automate.  Never-the-less, it did not work.

Krickner_0-1679506184382.png

 

I have been able to verify that the issue lies in the "field_4 (DueDate)" portion of the ODATA Filter Query, as I removed that portion and just left my job number and the flow ran successfully.  

When the flow ran successfully I was able to see the data format GET ITEMs was pulling from my Due Date field out of my SharePoint List, and it was "yyyy/MM/dd"  So, I adjusted the ODATA filter Query to match that format "

formatDateTime(items('Apply_to_each')?['DueDate'], 'yyyy/MM/ddT00:00:00.000Z')and it still didn't work.  😥 😪 
Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

No, it's nothing to do with the time format currently. I think the problem could be because of apply to each. I will try to replicate it on my end tomorrow. Hopefully someone else till then would get back to you.

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

 

I want you to try some things, can you filter with 1 condition at a time, lets see which one is giving error.

 

Try one more thing. Run the flow without any filter query. In the next step add a compose and in that pass the value expression you are getting from get items. Could be possible the field stored in Sharepoint for field_4 and Title could be different name. Though as you have already entered field_4 I am suspecting you have already done that.

 

Lastly, if one condition works, use a filter query action and filter the array you are getting from get items on the other condition. I found some posts where people have done that.

 

I hope this helps 🙂

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

 

and also instead of this : formatDateTime(items('Apply_to_each')?['DueDate'], 'yyyy/MM/ddT00:00:00.000Z')

use this:

formatDateTime(items('Apply_to_each')?['DueDate'], 'yyyy/MM/dd')

I tried filtering by just the Job Number (Title), and the flow worked.  I didn't try just filtering field_4 (Date), but I'll do that now.  Yeah, I verified the field names in Share Point.  Okay, so I should leave the ODATA filter in Get Items for SharePoint field (Title), but before the condition, I should insert a Filter Query action?

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

 

So, just keep Title in get items filter query.

 

After that get items, use filter array action and filter the array you are getting from get items on the field_4. 

@Sundeep_Malik the flow succeeded, but no data is getting created or edited.  I did a test by changing some of the data expecting the condition to see it as a new line item, and create a list item.  The flow runs, but it's almost as if it's skipping my condition (see below)

Krickner_1-1679681563890.png

 

 

Here is the result after the changes.

 

Krickner_2-1679681651036.png

 

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

Oh! See your filter array result is null, that's why it is getting skipped in condition. 

 

Now in filter query match the date formats by writing the formatDateTime function on both sides:

 

formatDateTime(duedateexpressionfromgetitems,'MM-dd-yyyy')

Equals 

formatDateTime(duedateexpressionfromexcel,'MM-dd-yyyy')

 

 

Or a format of your own choice.

 

I hope this helps 🙂

@Sundeep_Malik did I write these expressions wrong?  In both sets of data I have matching dates, but the Filter Array is coming back Null.  

 

Krickner_0-1679686251646.png

 

--------------------------------------------------------------------------------------------------------

 

Krickner_1-1679686388888.png

 

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

I am really confused here. Everything looks correct to me but even the input is coming as null. That shouldnt be happening. 😥

 

Input is the value you are getting from get items, that can never be null. I am sure you might have double checked that you are getting data from that get items. But I am really confused here.

Let me try it on a test data at my end.

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

So, I tried formatDateTime function on both sides of filter array and it worked.

 

Some things to notice:

 

1) The input is empty so you might not be getting something from get items

2) Try this: on left side only add due date dynamic expression, no item() function and on right side use formatDateTime function and match it to similarly stored in SharePoint. Or vice versa, on left formatdatetime function and on right directly due date from Excel value

3) Try this: Instead of item()[field_4] use item()[Duedate], use single quotes too. Hehe. 

@Sundeep_Malik 

It shows as pulling from Get Items, I tried to use the dynamic field on the left like you instructed and got the same result, null input on the Filter array.  I just don't understand why it's not showing any inputs.  The Filter array is in a Apply to each loop, is that causing an issue?

 

Krickner_0-1679689260455.png

 

Sundeep_Malik
Multi Super User
Multi Super User

@Krickner 

Oh! Correct. So for some of the iterations it might be null, check for other iterations is it working.

@Sundeep_Malik, I finally got it to work, and I really appreciate your help on this one.  Oddly enough, I returned to the original flow and made one adjustment.  When formatting the date on the ODATA filter, I had to use hyphens "-" instead of forward slashes "/", and I also had to use the format "MM-dd-yyyy."  I'm posting the entire flow so that others can benefit should they need a flow like this. 

  1. The flow waits for an excel sheet to upload to a specific SharePoint library, which triggers the flow.
  2. Creates an excel table within the excel sheet with existing data.
  3. Gets items from a SharePoint list and compares the Excel table to SharePoint items.
  4. If an item already exists in the SharePoint list, the flow updates the SharePoint list item.
  5. The flow creates a new SharePoint list item if the item does not exist.

This flow also uses a document upload status field to let users know when the flow has been completed.  You must delete this logic if you do not want to create a custom document upload status field in your SharePoint library.

Krickner_1-1679918583915.png

Krickner_3-1679919084198.png

Krickner_4-1679919270391.png

Krickner_6-1679919600852.png

Krickner_7-1679920281628.png

Krickner_8-1679920646108.png

Krickner_10-1679920951875.png

 

 

 

 

 

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (2,224)