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

Flow to trigger based on Sharepoint list date field

I have a Sharepoint list with a date field "Late Return".
I also have a calculated date field "Late Return chase due" which is set to 7 days after "Late Return".
I also have a date field "Received".

I'm trying to create a Flow which fires on the date in "Late Return chase due, and only if "Received" is null.  I've read many articles on the subject and I can't work out where I'm going wrong.  I continue to receive the "NO late return chaser" email.  I'd be really grateful for some help.

 

Capture.PNG

Condition is:

Late return chase due - is equal to - utcNow('dd-MM-yyyy')
Received - is equal to - null

 





1 ACCEPTED SOLUTION

Accepted Solutions

 

Hi @hungatebevis ,

 

Please try to add an integer variable to check if there are eligible items, if it does not exist, send the "NO late return chaser" email.

And you could add a Compose above Condition to check if the value of the date column is equal to the current date.

Then you could check the flow run history to find the cause of the error.

Image reference:

81.PNG82.PNG83.PNG

Hope this helps.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

7 REPLIES 7
Super User II
Super User II

hi@hungatebevis to compare nulls in sharepoint just you need to leave the field in condition blank or just write null not as a fuction just type null.

 

Please test it.



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me at www.christianabata.com Quieres contenido en español? Síguenos en Power Automate LA

Hi Christian, I just removed that altogether so I'm just left with

 

Late return chased due - equal to - utcNow('dd-MMMM-yy')

 

And it refuses to come back with a "yes".  It's really driving me crazy.

 

Bevis

 

@hungatebevis  the correct format is like 

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

 see the docs

 

https://docs.microsoft.com/en-us/azure/logic-apps/workflow-definition-language-functions-reference#f...



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me at www.christianabata.com Quieres contenido en español? Síguenos en Power Automate LA

Hmm, that wasn’t it either. The date field “Late return chase due was” a calculated field. I just ran an experiment on a non-calculated field, just a regular date field, and that has fixed it. The calculated date field was meant to be formatted as date only, but I’ve a feeling that wasn’t working in truth. So now I need a way around not being able to use the calculated date field, so I need a way to make the condition “Late return” date is 7 days ago. Any ideas?? Thanks! Bevis

Hi!
Hi!
As far as I know, Flow and calculated columns are not good friends. Did you consider replacing calculated column, using a single line of text instead (or whatever), and implement a flow that would do such calculations everytime the item is created or modified? Please note you must be careful not to enter in a neverending loop (i.e. item updated- flow executed - flow updates item - item updated - flow executed...)
Thanx!


Each time you click on any of our inspiring answers 'Thumb up' icon...
...an ewok scapes from the stormtroopers.

Be grateful, Thumbs up! Save the Galaxy for free!


Escribo sobre Power Automate en:
https://medium.com/anyone-can-automate/

Proud to be a Flownaut!



@hungatebevis 

As has been mentioned, you can't use a calculated column.  However, all you need to do is to use an addDays() expression in your condition or OData filter.  You can use a negative number with addDays().

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Scott

 

Hi @hungatebevis ,

 

Please try to add an integer variable to check if there are eligible items, if it does not exist, send the "NO late return chaser" email.

And you could add a Compose above Condition to check if the value of the date column is equal to the current date.

Then you could check the flow run history to find the cause of the error.

Image reference:

81.PNG82.PNG83.PNG

Hope this helps.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (74,238)