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

SharePoint column date -1, but acknowledge weekends?

Hi, 

 

I'm trying to figure out how to set a flow, which will take a already set date from a SharePoint column (date1) and than take -1 day and place it in another SharePoint column (date2). But the issue here is that if a date (date1) is set for Monday, -1 is Sunday, I want it to be set to the previous working day which is Friday(date2). 

 

Let say the date 1 is 30. July (Friday), date 2 should be 29 July(Thursday).

But if date 1 is 2. August (Monday), date 2 should be 30 July(Friday)

1 ACCEPTED SOLUTION

Accepted Solutions

@nikola_bgd I would expand slightly on @eric-cheng's excellent answer, by using a very quick Do until method with a list of days.

 

  1. Create a "prvDayVAR" string variable, a "prvDateVAR" string variable, and an array variable that is either "weekDaysArrVAR" or "wkdDaysArrVAR".
  2. Create a "Do until"
  3. Subtract from your prvDayVAR date until your array contains the value in your prvDay. 🙂

Here's the flow, I'll break it down in an edit, or followup post, soon. But accounting for bank hols, etc, is a different matter, and you'd need an extra condition that checks if the date exists (for example) on a SharePoint list, or something.

 

0 - Full Flow.jpg

 

Setup - The Variables

Ignoring my dateVAR, which I would use whether or not I had a source from elsewhere, this is all pretty much as mentioned.

1 - Variables.jpg

 

The reason that the prvDay and prvDate are set to the current date in the initialising state, is because your 'Do until' will fail with blank variables, and if you perform one date minus before the 'Do until' you'll need to add a condition.

 

Execution - 'Do until' Action

This will keep running until the prvday value is one that matches any of the values in the list inside the workDaysArrVAR. Once it has reached that, the prvday and prv date variables will be set to the previous working day value and usable elsewhere in the flow.

2 - Do Until Other As You Would Have Done Until You.jpg

 

Expressions Used

There's only one expression used here, the one to display the date/time as just the name of the day. The "Calculated time" reference in the 'Do until' set prvDate action refers to the step before it which subtracts 1 day from the date.

 

Here it is in the initialising step:

formatDateTime(variables('dateVAR'), 'dddd')

... and here it is in the set step inside the 'Do until':

formatDateTime(body('Subtract_from_time_1_day_repeater'), 'dddd')

That's actually it!

 

The bonus with this method is that you'll also now have those variables set and usable elsewhere in the flow for other stuff (if you perform all this early on).

View solution in original post

7 REPLIES 7
eric-cheng
Solution Sage
Solution Sage

Hi @nikola_bgd ,

 

Please refer to one of my previous posts here.

 

Thanks

 

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

@nikola_bgd I would expand slightly on @eric-cheng's excellent answer, by using a very quick Do until method with a list of days.

 

  1. Create a "prvDayVAR" string variable, a "prvDateVAR" string variable, and an array variable that is either "weekDaysArrVAR" or "wkdDaysArrVAR".
  2. Create a "Do until"
  3. Subtract from your prvDayVAR date until your array contains the value in your prvDay. 🙂

Here's the flow, I'll break it down in an edit, or followup post, soon. But accounting for bank hols, etc, is a different matter, and you'd need an extra condition that checks if the date exists (for example) on a SharePoint list, or something.

 

0 - Full Flow.jpg

 

Setup - The Variables

Ignoring my dateVAR, which I would use whether or not I had a source from elsewhere, this is all pretty much as mentioned.

1 - Variables.jpg

 

The reason that the prvDay and prvDate are set to the current date in the initialising state, is because your 'Do until' will fail with blank variables, and if you perform one date minus before the 'Do until' you'll need to add a condition.

 

Execution - 'Do until' Action

This will keep running until the prvday value is one that matches any of the values in the list inside the workDaysArrVAR. Once it has reached that, the prvday and prv date variables will be set to the previous working day value and usable elsewhere in the flow.

2 - Do Until Other As You Would Have Done Until You.jpg

 

Expressions Used

There's only one expression used here, the one to display the date/time as just the name of the day. The "Calculated time" reference in the 'Do until' set prvDate action refers to the step before it which subtracts 1 day from the date.

 

Here it is in the initialising step:

formatDateTime(variables('dateVAR'), 'dddd')

... and here it is in the set step inside the 'Do until':

formatDateTime(body('Subtract_from_time_1_day_repeater'), 'dddd')

That's actually it!

 

The bonus with this method is that you'll also now have those variables set and usable elsewhere in the flow for other stuff (if you perform all this early on).

Thanks! Works well

 

Btw do have a solution, to a situation where the user has not set any date? so the date input to another field is also empty? 
When I use this flow it fails.

I do, @nikola_bgd !

 

In short (I will go long when I can, but I'm busy right now) there are a few choices that I can think of quickly (there are other options, too!) so I've listed them below:

  1. Error Branching - You can create an error branch using the "Configure run after" option and set a failure branch only to run on "Failed". If you do this, you must ensure that afterwards you set a follow up action with TWO "run after" setups in it that will run whatever happens in either success or failure branches.
  2. Condition - You can set a "Condition" action to check if there is a value there, and if not, to place a defined, old, date in there, or trigger some other action (maybe an email to the person, I don't know).
  3. SharePoint Verification - You can set up certain fields as required (if the usage allows it) in SharePoint, to always get a date.
  4. SharePoint Auto-Date - You could set up a default value for the field in SharePoint, or an additional calculated column that checks for data there. Then if the default value is still set when submitted you can have the flow act however you like with that information. 🙂

 

Of all of these, the easiest to implement is the "Condition" one, which you can figure out the logic for yourself. Perhaps even one day distil it into one expression! But it will at least check for blank data.

 

Here's what the run after option looks like on any action in Power Automate, just click the action's menu dots:

error.jpg

 

There's lots of documentation on how to use that, but if you're unsure, just make some test flows elsewhere with dummy inputs. 🙂

 

Oh ... and ... finally ... if you're using SharePoint, you could do some of this work in the columns there, using the default values, and using calculated columns, etc. This allows you to rely less on Power Automate, should you wish to have some data be native for other integrations.

Hey @eliotcole

 

I've tried the first method but somehow the flow fails:

 

nikola_bgd_0-1627308866030.png

 

Update item on the left is when the flow is successful, 

Update item on the right is when it's not and let say I enter a blank date, the right update item activates, but the entire flow is marked as failed.  

 

Btw, thanks a lot for helping

 

Yep, that's good, @nikola_bgd , that's why I said that you need to create *another* action after those, to kind of "close the loop" as it were.

Can you help with another problem here, I've tried to figure it out, no luck.. 

The solution you posted here is perfect, however can I have another "IF" here, if the date = TODAY, just leave it than to TODAY

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,647)