Hello.
I need to send email after 4 work days (from Monday to Friday) after creating file in SharePoint document library.
Which way is better to do that?
Solved! Go to Solution.
@ppl ,
I would suggest using an expression to calculate how many work days it has been between the created date of the SP file and today's date. You can then use a condition to evaluate if that number of days is equal to 4.
The logic behind excluding Saturday and Sunday from the calculation could be along the lines of subtracting two days from the the "days since" calculation if the date created was Wednesday through Friday (assuming you want the email to send on the 4th day). The dayOfWeek() expression is helpful here; it returns an integer between 1-7 (where Monday is 1 and Sunday is 7) representing the day of the week of the date passed into it.
So:
dayOfWeek('11-18-2020')
would return 3, since Wednesday is the third day of the week.
This is what I came up with (though I used a planner plan instead of a Sharepoint directory to get my "createdDate" values. My assumption in this solution is that the email is to be sent on the fourth day including the date the item was created. So if the item was created on Monday, the email will be sent on Thursday.
Technically the two expressions in the two Compose actions could be combined into one...but it would be a longer expression. Here are the two expressions and their explanations:
if(lessorequals(dayofweek(items('Apply_to_each')?['createdDateTime']),2),0,2)
this evaluates what day of the week the item was created on and creates an "adjustment" value to account for the two weekend days if the fourth day would be Saturday or Sunday. if the created day is a Monday or Tuesday, no adjustment is needed, hence zero. if the created day is Wednesday through Friday, we'll have to add two extra days to get past the weekend.
addDays(items('Apply_to_each')?['createdDateTime'], add(3,outputs('Compose_4')), 'MM-dd-yyy')
this adds three days (plus the "adjustment" value) to the file's dateCreated date to get the fourth work day after the file was created.
the Condition evaluates whether the date of the fourth workday after the file was created equals today or not. It is important to make sure that both dates are formatted the same, or it may always evaluate as false.
I hope this helps
thanks,
Kyle
@ppl ,
I would suggest using an expression to calculate how many work days it has been between the created date of the SP file and today's date. You can then use a condition to evaluate if that number of days is equal to 4.
The logic behind excluding Saturday and Sunday from the calculation could be along the lines of subtracting two days from the the "days since" calculation if the date created was Wednesday through Friday (assuming you want the email to send on the 4th day). The dayOfWeek() expression is helpful here; it returns an integer between 1-7 (where Monday is 1 and Sunday is 7) representing the day of the week of the date passed into it.
So:
dayOfWeek('11-18-2020')
would return 3, since Wednesday is the third day of the week.
This is what I came up with (though I used a planner plan instead of a Sharepoint directory to get my "createdDate" values. My assumption in this solution is that the email is to be sent on the fourth day including the date the item was created. So if the item was created on Monday, the email will be sent on Thursday.
Technically the two expressions in the two Compose actions could be combined into one...but it would be a longer expression. Here are the two expressions and their explanations:
if(lessorequals(dayofweek(items('Apply_to_each')?['createdDateTime']),2),0,2)
this evaluates what day of the week the item was created on and creates an "adjustment" value to account for the two weekend days if the fourth day would be Saturday or Sunday. if the created day is a Monday or Tuesday, no adjustment is needed, hence zero. if the created day is Wednesday through Friday, we'll have to add two extra days to get past the weekend.
addDays(items('Apply_to_each')?['createdDateTime'], add(3,outputs('Compose_4')), 'MM-dd-yyy')
this adds three days (plus the "adjustment" value) to the file's dateCreated date to get the fourth work day after the file was created.
the Condition evaluates whether the date of the fourth workday after the file was created equals today or not. It is important to make sure that both dates are formatted the same, or it may always evaluate as false.
I hope this helps
thanks,
Kyle
@Anonymous
Interesting solution. Thank you!
But I have an error in this step
@ppl ,
According to the error, there is a problem with the output of "items('Apply_to_each')?['Сreated']" in that it is not returning a DateTime but rather is empty.
if you put a Compose into your loop and pass in the "body" of "Get Files" the output should allow you to see all of the available data.
Share a screenshot of that, if you would.
thanks,
Kyle
@Anonymous
@ppl,
I am not able to re-create your error...and i'm using SP files now instead of Planner tasks in my test Flow.
instead of the whole body in the test "Compose" just pass in the "Created" field and see what it returns.
The error is suggesting that it's returning nothing, but your most recent screenshot clearly shows that there is data in the "Created" field. This leads me to believe that we're using the wrong "address" (the JSON expression that identifies the data we want). However, I'm using the same syntax and it seems to be working for me...
So, before running the flow, hover your cursor over the dynamic content in the Compose field and record what the actual JSON is to access that field.
If you would, share both of those.
We'll get to the bottom of this.
thanks,
Kyle
@Anonymous
This is what Compose of Created returns
And JSON code of it
@ppl,
this is weird...are any of the 22 records returning nothing for that field?
That wouldn't make any sense, because every item would have a Created date...but that's the only thing I can think of...
the "if()" expression looks right. In fact, it matches mine exactly...
And, based on the compose that you inserted, it does look like you've got the right expression to pull the Created Date.
the only thing I can suggest at this point is to pare back the expression and troubleshoot it by building it step by step. add just the "dayofweek()" expression around "Created" in your test Compose and see what it returns.
I wish I had something more specific, but, like I said, I'm not able to recreate your issue.
thanks,
Kyle
Episode Seven of Power Platform Connections sees David Warner and Hugo Bernier talk to Dian Taylor, alongside the latest news, product reviews, and community blogs. Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.
Super Users – 2023 Season 1 We are excited to kick off the Power Users Super User Program for 2023 - Season 1. The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts. Super User Season 1 | Contributions July 1, 2022 – December 31, 2022 Super User Season 2 | Contributions January 1, 2023 – June 30, 2023 Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile. Power Apps Power Automate Power Virtual Agents Power Pages Pstork1* Pstork1* Pstork1* OliverRodrigues BCBuizer Expiscornovus* Expiscornovus* ragavanrajan AhmedSalih grantjenkins renatoromao Mira_Ghaly* Mira_Ghaly* Sundeep_Malik* Sundeep_Malik* SudeepGhatakNZ* SudeepGhatakNZ* StretchFredrik* StretchFredrik* 365-Assist* 365-Assist* cha_cha ekarim2020 timl Hardesh15 iAm_ManCat annajhaveri SebS Rhiassuring LaurensM abm TheRobRush Ankesh_49 WiZey lbendlin Nogueira1306 Kaif_Siddique victorcp RobElliott dpoggemann srduval SBax CFernandes Roverandom schwibach Akser CraigStewart PowerRanger MichaelAnnis subsguts David_MA EricRegnier edgonzales zmansuri GeorgiosG ChrisPiasecki ryule AmDev fchopo phipps0218 tom_riha theapurva takolota Akash17 momlo BCLS776 Shuvam-rpa rampprakash ScottShearer Rusk ChristianAbata cchannon Koen5 a33ik Heartholme AaronKnox okeks Matren David_MA Alex_10 Jeff_Thorpe poweractivate Ramole DianaBirkelbach DavidZoon AJ_Z PriyankaGeethik BrianS StalinPonnusamy HamidBee CNT Anonymous_Hippo Anchov KeithAtherton alaabitar Tolu_Victor KRider sperry1625 IPC_ahaas zuurg rubin_boer cwebb365 Dorrinda G1124 Gabibalaban Manan-Malhotra jcfDaniel WarrenBelz Waegemma drrickryp GuidoPreite If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances. Once they are received the list will be updated.
Join us for an in-depth look into the latest updates across Microsoft Dynamics 365 and Microsoft Power Platform that are helping businesses overcome their biggest challenges today. Find out about new features, capabilities, and best practices for connecting data to deliver exceptional customer experiences, collaborating, and creating using AI-powered capabilities, driving productivity with automation—and building towards future growth with today’s leading technology. Microsoft leaders and experts will guide you through the full 2023 release wave 1 and how these advancements will help you: Expand visibility, reduce time, and enhance creativity in your departments and teams with unified, AI-powered capabilities.Empower your employees to focus on revenue-generating tasks while automating repetitive tasks.Connect people, data, and processes across your organization with modern collaboration tools.Innovate without limits using the latest in low-code development, including new GPT-powered capabilities. Click Here to Register Today!
We are excited to share the ‘Power Platform Communities Front Door’ experience with you! Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well. Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities. Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform. Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.
We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida. Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more. Register today: https://www.powerplatformconf.com/
User | Count |
---|---|
95 | |
35 | |
27 | |
25 | |
21 |
User | Count |
---|---|
122 | |
57 | |
42 | |
41 | |
40 |