Checking SharePoint list for due date, send email notifying item is due tomorrow

[Anonymous]

Hello!

Pretty new to all of this, but I have made a few flows that use our SharePoint list.

My current project is getting items out of a SharePoint list, checking a due date for a task from there, comparing that date to today, and then sending out an email letting the person in charge of the task know they have stuff due tomorrow. 

The flow I have built works fine down until sending the email.

I get the error: 

My entire flow:

Any ideas why this isn't working?

-Matt

[yiyingjiao]

Hi @Anonymous ,

  At the condition I see two "conveter..". Are they the dates that you got from the previous steps? May I please see the expressions of them?

I'm looking at the error message itself and it seems like that, rather than going through every single object in an array and performing actions on it, the flow just looks at one single object. My guess is that the condition is not checking on the date objects you've set up in steps above but I'm just guessing.  It will be great if you could share more details!

Yiying Jiao

Support Engineer

Microsoft Power Platform

[Anonymous]

Hello @yiyingjiao!

yes, the flow looks at the SharePoint items and finds the due date for tasks that are still in a not completed state, then converts that to Pacific time, then subtracts a day from the due date. It then compares that due date to today, and if they are =, then it is supposed to send an email to the person who is in charge of finishing that task.

Here, it found 4 un-finished tasks, and one of them is due tomorrow. This is the task that passed the condition as true, but as you can see it didn't generate an email.

-Matt

[yiyingjiao]

Hi @Anonymous ,

  Thank you for sharing the details! I appreciate it! I notice there are two "apply to each" loops with one inside the other: First loop is to check and compare time, then inner loop to send an email. May I ask if your inventory is made up of rows of different tasks, each with its due date column and link column entries)? Or is it grouped in some way that there are nested information inside each row, like one row as multiple tasks?

I'm asking because the outer loop works successfully but the inner loop gives error. It's expecting an array but only get an object. If it's like the first scenario, and the previous 'get items' action gives you the access to each row, I think you may discard the inner "apply to each" loop.  Just send the email directly after "If yes", because the outer "apply to each" loop already brings you to the correct level. 

If there are multiple tasks inside one row, or the link you want to send and some other values are all in one single column, then yes : you need the inner "apply to each" loop to bring you one level further down. To fix the error, before you enter the inner loop(right after "if yes") you want to save your current item into an array variable. Then apply the inner loop on that array.

I hope this can provide some help! Looking forward to learning how it goes and please let me know if you still run into any error.

Yiying Jiao

Support Engineer

Microsoft Power Platform

If this post helps, then please consider accepting it as the solution to help other members find it more quickly! Have a great day!

[Anonymous]

Hello @yiyingjiao!

When populating the email with dynamic content (email addresses from the SharePoint list), power automate automatically creates that "apply to each". It does this both for when I enter the requestor's email and the assignee's email.

I moved my email portion out of the "apply to each", and then deleted it, so my flow looked like this:

I ran it and got this error message for the task that passed the condition:

And when going back to the flow, I noticed these values have changed:

Here is our SharePoint list. 

Each task is its own row.

-Matt

[yiyingjiao]

Hi @Anonymous ,

     I apologize for the late reply. Are you still experiencing issues with the flow? I think you are doing everything correctly here, but the flow isn't behaving as expected. The best option to resolve this issue will be to submit a support request to Power Platform team so we can inspect the flow at more depth and provide much more timely communications.

   Here's the flow I created following your template. It works for me and I receive emails about products that are about to expire in 5 days, just as expected. The product inventory I used is also a Sharepoint List.

Yiying Jiao

Support Engineer

Microsoft Power Platform

If this post helps, then please consider accepting it as the solution to help other members find it more quickly! Have a great day!