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

Checked OUT Alert - If files checked out for more than 1 hour

I have a flow that runes everytime when someone checks out a file on sharepoint but it has one problem when the same user checks out the file again, it sends duplicate reminders. Suppose:

 

User 1 checked OUT a document xuz.xlsx at 11:00 AM

Flow triggered - Lets call it A

User 1 checked IN/ discarded xyz.xlsx at 11:10 AM

User 1 checked OUT the document again at 11:12 AM

Flow triggered - Lets call it B

 

The flow A does not end until 1 hour and it sends an email after checking the file is still check out or not (the file is indeed check out but under Flow B and not A). In this case the first flow should end and it should not send an email.

 

aakkuummaarr_0-1681116304478.png

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @aakkuummaarr 

 

One idea strikes to my mind. Since for this case, even same user is checkout file at different times but within one hour, but the modified time would be different right , let's say user A check out file at 11:00 am flow A triggers , while user A checks again at 11:30 am, while will triggers flow B. then before sending email, if we check whether the modified date at start of trigger and after delay of one hour , and if it is same it means user has edited/ checkout file after trigger has started, so email can be sent, if it is not same, this means same user has checked out in some time after first checkout has been done.

 

So from flow perspective, you have to add this condition while sending email in your flow

 

Nived_Nambiar_2-1682614479627.png

 

 

 

 

Nived_Nambiar_0-1682614435675.png

 

Nived_Nambiar_1-1682614464110.png

 

 

 

So by this, flow A will end , since modified before and after delay would be different, so it wont send any email

and flow B would send email, since for it modified time before and after would be same 🙂

 

Sorry for late response !

 

Let me know if you have any questions 🙂

 

View solution in original post

15 REPLIES 15

Hi @aakkuummaarr 

 

Just to confirm, you want flow B to end or flow A to end ?

If the same user checks in/discards the file before 1 hour completedm the first triggered flow should not communicate with the second triggered flow (here, the second triggered flow is also due to the same person checking out the same file again).

 

If the person is different, the flow ends automatically because I have asked the flow to make sure that the Checkout user before delay and after delay should be same.

 

Its the same person checking out the file again with in 1 hour creating the email duplicates.

So for both cases Flow B should end ?

Hi, sorry let me explain: The flow triggers when someone checks out the file.

 

There are 3 conditions:

1. Person A checked out, flow triggered to wait until 1 hour (Do Until) and the person checked in the file before 1 hour. Flow sent no email notification.

2. Person B checked out, another flow triggered to wait until 1 hour and the person did not check in/discard, flow sent an email asking them to let other team members edit the sheet by releasing the sheet lock.

 

The above 2 tickets are working fine.

 

3. Now comes the third condition where a person checked out the file and flow got triggered and is now waiting for 1 hour to complete.

Now note, even though the person checks-in the file in 5/10 minutes, and checked out the file again on 59th minute, the flow that is currently running to complete its 1 hour is now supposed to check if the file is checked out and if yes: 'to whom'

Unfortunately, as per the flow the person at the beginning of Do Until and the person at 59th minute of that ongoing flow is same and thus it will tell that user to close the sheet saying 'you have the sheet checked out for 1 hour', while the reality is that the person checked out at the begging of the hour and at the end only.

 

There is no break in this flow unfortunately and thus it is resulting in double emails. Assume I checkout the file , check in and check out again to leave it as it is for 1 hour, I'll get 2 emails.

 

I hope I could explain it now.

@Nived_Nambiar Hey, does the info help?

Hi @aakkuummaarr 

 

Yes it helps me 

 

So your problem is you want to prevent the occurence of 2 duplicated emails .

 

Also if i am right, the two emails are coming after an hour delay right , that is one hour delay after other email arrives ?

 

 

@Nived_Nambiar right about the first part you mentioned.

 

If ABC checks out the file at 11:00 AM, checks in at 11:30 and checks out the same file again at 11:31 (2 flaws have been triggered for 2 check outs) and does not checks in the file till 12:00 (1 hour = true for first flow)) or even till 12:30 (1 hour = true for 1st flow, 1 hour = false for second flow) , he gets one email.

If he does not checks-in the file till 12:31 (1 hour = true for second flow), he gets 2 emails for both triggers.

 

In this case, he should only be getting an email for keeping the file checked out for one hour continuously which is true for second case only.

any update? @Nived_Nambiar 

@Nived_Nambiar any update brother?

Hi @aakkuummaarr 

 

One idea strikes to my mind. Since for this case, even same user is checkout file at different times but within one hour, but the modified time would be different right , let's say user A check out file at 11:00 am flow A triggers , while user A checks again at 11:30 am, while will triggers flow B. then before sending email, if we check whether the modified date at start of trigger and after delay of one hour , and if it is same it means user has edited/ checkout file after trigger has started, so email can be sent, if it is not same, this means same user has checked out in some time after first checkout has been done.

 

So from flow perspective, you have to add this condition while sending email in your flow

 

Nived_Nambiar_2-1682614479627.png

 

 

 

 

Nived_Nambiar_0-1682614435675.png

 

Nived_Nambiar_1-1682614464110.png

 

 

 

So by this, flow A will end , since modified before and after delay would be different, so it wont send any email

and flow B would send email, since for it modified time before and after would be same 🙂

 

Sorry for late response !

 

Let me know if you have any questions 🙂

 

@Nived_Nambiar 

Hey, before I try it, are you sure power automate captures check-out time as modified time? I have heard it does not?

@Nived_Nambiar - This condition is failing as I think check-out time is not = modified time.

 

Is there another way to capture checkout time?

CheckOUT time is captured by:

triggerOutputs()?['headers']?['Last-Modified']

 

I added this as a condition and compared the checkOUT time before and after the delay. Worked.

Hi @aakkuummaarr 

 

is it returning last modfiied time itself ?

 

Hi @Nived_Nambiar 

 

Yes, it does but There is still an issue with it, this is limited to the CheckOUTtime-1 event, and even with CheckOUTtime-2, it gives the same output as CheckOUTtime-1.

 

I am unsure how can I capture the fresh output at the second trigger so that it knows if anyone else checked it out after the 1-hour delay.

 

aakkuummaarr_0-1684388050159.png

 

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