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

Future TimeStamp

Hello,

 

I want to create a solution where I can hardcode the timestamp of any timestamp that is Friday at 17:00 or greater and less than Monday 08:00 (The next week).

 

Example:

 

2023-10-20T17:01:00Z

2023-10-21T19:00:00Z

2023-10-22T15:00:00Z

2023-10-23T07:59:00Z

etc...

 

Output: 

Hardcode timestamp - 2023-10-24T15:00:00Z

1 ACCEPTED SOLUTION

Accepted Solutions

Ok this isn't really elegant, but this is all I can come up with on Friday afternoon. It is basically 4 separate expressions checking the datetime value. Then the expressions are all combined into one.

 

  1. If the dayofweek() is Friday (5) and the time hour is greater or equal 17; then add 4 days.
  2. If the dayofweek() is Saturday (6) then add 3 days.
  3. If the dayofweek() is Sunday (0) then add 2 days.
  4. If the dayofweek() is Monday (1) and the time hour is less or equal 7; then add 1 day.

There is also some clean up functions like startofDay() that way it sets the time to midnight and I just added 15 hours so that it will be 3pm/15:00 on the Tuesday.

 

Expression 1: If day of Week is Friday and after 5:00pm

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(5)),greaterOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(17))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),4),15),variables('SPCreatedDateTime'))

Expression 2: If day of week is Saturday

if(equals(dayofWeek(variables('SPCreatedDateTime')),int(6)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),3),15),variables('SPCreatedDateTime'))

Expression 3: If day of week is Sunday

if(equals(dayofWeek(variables('SPCreatedDateTime')),int(0)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),2),15),variables('SPCreatedDateTime'))

Expression 4: If day of week is Monday and hour is 7 or less

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(1)),lessOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(7))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),1),15),variables('SPCreatedDateTime'))

 

Combining all of the expressions together, basically removing the last part of each if() and replacing it with the next expression. 

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(5)),greaterOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(17))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),4),15),if(equals(dayofWeek(variables('SPCreatedDateTime')),int(6)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),3),15),if(equals(dayofWeek(variables('SPCreatedDateTime')),int(0)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),2),15),if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(1)),lessOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(7))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),1),15),variables('SPCreatedDateTime')))))

 

Here is a screenshot of the flow I used to make and test this. It has the separate expressions just for testing, they aren't required to be present. I used a variable called SPCreatedDateTime.

The 4 separate expressions are all included in the final compose.The 4 separate expressions are all included in the final compose.

Changing the datetime in my variable I was able to get the output to work correctly.

 

I went ahead and made a flow using "When an item is created" from SharePoint and then put the expression using the Created datetime. However, I wasn't able to test this since I obviously can't make an item in the future. I basically replaced my variable from the previous example with the sharepoint dynamic content Created.

This uses the SP Created datetime output in the expression. (I was not able to test this.)This uses the SP Created datetime output in the expression. (I was not able to test this.)

Here is the expression with the SharePoint example:

if(and(equals(dayofWeek(triggerOutputs()?['body/Created']),int(5)),greaterOrEquals(int(formatDateTime(triggerOutputs()?['body/Created'],'HH')),int(17))),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),4),15),if(equals(dayofWeek(triggerOutputs()?['body/Created']),int(6)),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),3),15),if(equals(dayofWeek(triggerOutputs()?['body/Created']),int(0)),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),2),15),if(and(equals(dayofWeek(triggerOutputs()?['body/Created']),int(1)),lessOrEquals(int(formatDateTime(triggerOutputs()?['body/Created'],'HH')),int(7))),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),1),15),triggerOutputs()?['body/Created']))))

 

Hope this works for you,

 

If you want to look at the functions that were used check Reference Guide for Expression Functions.

if()

equals()

and()

int()

greaterOrEquals()

lessOrEquals()

formatDateTime()

dayofWeek()

startofDay()

addHours()

 

There might be a more clever way to approach this to make it not such a hammer of an expression, but I can't think of it right now. The benefit of this method is that it would work for any datetime past or future if it was run through. It would change it to the tuesday after that created date.

 

Good luck!

View solution in original post

11 REPLIES 11

Is this for this weekend only? Can you explain more about the function of this hardcode timestamp? 

 

It can be done by basically checking if the day of the week is Saturday or Sunday, then give out hardcode. Check if day of week is Friday, if so, is it after 5pm, then give out hardcode. Check if day of week is Monday, if so, is it before 8 am, then give out hardcode.

 

It would be easier to make an example if you could talk about your source time and what this is for. Or else I will be making something that works specifically for this text, and might not be best for what you want to use for a flow.

Hi @wskinnermctc ,

No, it's not only for the weekend, it's basically any timestamp from Friday 17:00 onwards and before Monday 08:00.

 

The timestamp can be either Friday (Equal or greater than 17:00) or Monday 08:00(Less than).

 

My source time comes from a SharePoint List Column called created. A record can be created out of business hours from Friday 17:00 onwards until Monday 08:00 the next week. I just need a way to hardcode this timestamp 2023-10-24T15:00:00Z for any timestamp falls into that condition.

 

2023-10-20T17:01:00Z

2023-10-20T22:01:00Z

2023-10-21T19:00:00Z

2023-10-21T20:00:00Z

2023-10-22T15:00:00Z

2023-10-22T17:00:00Z

2023-10-23T05:59:00Z

2023-10-23T07:59:00Z

etc ...

 

Output: 

Hardcode timestamp - 2023-10-24T15:00:00Z

I understand the time range is Friday 5:00pm - Monday 7:59am.

 

I'm asking about is this flow literally going to be only used for today Oct 20 - through monday Oct 23rd. This weekend.

 

Or will you be trying to do this again next weekend 27th-30th? and/or the weekend after Nov 3rd-6th? Like will this flow need to adjust as time goes on?

@wskinnermctc - sorry, I misunderstood you the first time.

 

The flow would need to adjust to all upcoming weekends

Ok this isn't really elegant, but this is all I can come up with on Friday afternoon. It is basically 4 separate expressions checking the datetime value. Then the expressions are all combined into one.

 

  1. If the dayofweek() is Friday (5) and the time hour is greater or equal 17; then add 4 days.
  2. If the dayofweek() is Saturday (6) then add 3 days.
  3. If the dayofweek() is Sunday (0) then add 2 days.
  4. If the dayofweek() is Monday (1) and the time hour is less or equal 7; then add 1 day.

There is also some clean up functions like startofDay() that way it sets the time to midnight and I just added 15 hours so that it will be 3pm/15:00 on the Tuesday.

 

Expression 1: If day of Week is Friday and after 5:00pm

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(5)),greaterOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(17))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),4),15),variables('SPCreatedDateTime'))

Expression 2: If day of week is Saturday

if(equals(dayofWeek(variables('SPCreatedDateTime')),int(6)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),3),15),variables('SPCreatedDateTime'))

Expression 3: If day of week is Sunday

if(equals(dayofWeek(variables('SPCreatedDateTime')),int(0)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),2),15),variables('SPCreatedDateTime'))

Expression 4: If day of week is Monday and hour is 7 or less

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(1)),lessOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(7))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),1),15),variables('SPCreatedDateTime'))

 

Combining all of the expressions together, basically removing the last part of each if() and replacing it with the next expression. 

if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(5)),greaterOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(17))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),4),15),if(equals(dayofWeek(variables('SPCreatedDateTime')),int(6)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),3),15),if(equals(dayofWeek(variables('SPCreatedDateTime')),int(0)),addhours(addDays(startofDay(variables('SPCreatedDateTime')),2),15),if(and(equals(dayofWeek(variables('SPCreatedDateTime')),int(1)),lessOrEquals(int(formatDateTime(variables('SPCreatedDateTime'),'HH')),int(7))),addhours(addDays(startofDay(variables('SPCreatedDateTime')),1),15),variables('SPCreatedDateTime')))))

 

Here is a screenshot of the flow I used to make and test this. It has the separate expressions just for testing, they aren't required to be present. I used a variable called SPCreatedDateTime.

The 4 separate expressions are all included in the final compose.The 4 separate expressions are all included in the final compose.

Changing the datetime in my variable I was able to get the output to work correctly.

 

I went ahead and made a flow using "When an item is created" from SharePoint and then put the expression using the Created datetime. However, I wasn't able to test this since I obviously can't make an item in the future. I basically replaced my variable from the previous example with the sharepoint dynamic content Created.

This uses the SP Created datetime output in the expression. (I was not able to test this.)This uses the SP Created datetime output in the expression. (I was not able to test this.)

Here is the expression with the SharePoint example:

if(and(equals(dayofWeek(triggerOutputs()?['body/Created']),int(5)),greaterOrEquals(int(formatDateTime(triggerOutputs()?['body/Created'],'HH')),int(17))),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),4),15),if(equals(dayofWeek(triggerOutputs()?['body/Created']),int(6)),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),3),15),if(equals(dayofWeek(triggerOutputs()?['body/Created']),int(0)),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),2),15),if(and(equals(dayofWeek(triggerOutputs()?['body/Created']),int(1)),lessOrEquals(int(formatDateTime(triggerOutputs()?['body/Created'],'HH')),int(7))),addhours(addDays(startofDay(triggerOutputs()?['body/Created']),1),15),triggerOutputs()?['body/Created']))))

 

Hope this works for you,

 

If you want to look at the functions that were used check Reference Guide for Expression Functions.

if()

equals()

and()

int()

greaterOrEquals()

lessOrEquals()

formatDateTime()

dayofWeek()

startofDay()

addHours()

 

There might be a more clever way to approach this to make it not such a hammer of an expression, but I can't think of it right now. The benefit of this method is that it would work for any datetime past or future if it was run through. It would change it to the tuesday after that created date.

 

Good luck!

@wskinnermctc  - Sorry for taking so long to respond. Your solution worked like a charm and I really appreciate all the effort you have put into figuring this expression.

 

Your expression is just part of a bigger solution that I was building with many conditions and composes.

 

Is it possible for you help me with converting my solution from conditions and compose to pure expression solution?

Hi @wskinnermctc , Can you help me help me with excluding public holidays on the same solution you provided?

 

Example:

16 December

25 December

1 January 

@Caleb62881177 I don't think using an expression would be the best approach with the holidays. It would be too many nesting. 

Also, if you think about it, the first expression I made that was just about skipping the weekends doesn't help if a holiday is on a Tuesday and/or some other weird things I probably not thinking about.

 

You will probably need some method where you list the holiday dates and then compare the date to all of the dates in that list. You can make an array and put in dates, then have the flow go through them. Similarly, you could have like a SharePoint list of dates that include company holidays or something and go through that list.

 

Are you going to want to include company holidays?

 

 

@wskinnermctc  - No, just public holidays.

@wskinnermctc - An array with the different dates would works for my solution. I am not sure how to loop through the Get Items and Array with an Apply To Each. 

 

sharepoint.jpg

@wskinnermctc , I just want to make sure if I am on the right track.

 

loop1.jpg

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 (1,808)