cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
nikola_bgd
Advocate II
Advocate II

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
eliotcole
Super User
Super User

@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

eliotcole
Super User
Super User

@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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,879)