I have created an audit app using PowerApps. I have not been able to figure out how to automatically time how long it takes the auditor to complete the audit. I would like the app to start timing when the audit form is opened and then stop timing when the submit button is selected. I would then like the duration data to populate into a column in the SharePoint list where the rest of the audit data is collected. Anyone know how to do this?
Solved! Go to Solution.
Hi Guys,
I'm just curious as to why we think it's necessary to use a timer here?
Could we not just store the time that the user opens the screen into a variable (eg on the OnVisible property of the screen)? Then on the Submit button, we can work out the duration by calculating the difference between the current time and the initial time.
@Anonymous - if you're really stuck with implementing the timer technique that that @Mr-Dang-MSFT and @BenFetters describes, I can probably give you a fuller explanation of what I described above.
Hi @Anonymous,
You will want to learn about the timer control:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-timer
Timers have an AutoStart property where you can place a condition on when it should be starting. Accordingly, they will stop when the same condition is false.
You can give a timer a very long duration so they do not end before the audit is complete.
When you write the data back to SharePoint, you would save Timer1.Value. That returns the elapsed time in milliseconds. If you prefer seconds, divide Timer1.Value/1000. If you would like the time formatted in hh:mm:ss, then you could use the Time() function:
Time(0,0,Timer1.Value/1000)
It will regroup all the seconds into h and m accordingly. Saving that format would need a text column in SharePoint though.
Hi,
I have an idea that hopefully can help. Please let me know if you have questions because I know explanations can be kind of confusing!
First, I would add a timer to the screen that you have the form on. Then set the timer's "AutoStart" property to true. Then, on the form there is an "OnSuccess" property - set this to this formula: Patch(YourDataSourceName, YourFormName.LastSubmit, {Duration: Timer1.Text}) you might need to say Value(Timer1.Text) depending on what the type of field it is.
Lastly, for your submit button, be sure to add this formula to the END of the "OnSelect" property: Reset(Timer1)
I hope this makes sense and was helpful.
Ben
Hi Guys,
I'm just curious as to why we think it's necessary to use a timer here?
Could we not just store the time that the user opens the screen into a variable (eg on the OnVisible property of the screen)? Then on the Submit button, we can work out the duration by calculating the difference between the current time and the initial time.
@Anonymous - if you're really stuck with implementing the timer technique that that @Mr-Dang-MSFT and @BenFetters describes, I can probably give you a fuller explanation of what I described above.
@BenFetters, I like how you also described how to restart the timer.
@timl, now that I think about it, I like the idea of saving the start time and end time, then calculating the elapsed time later. That is more manageable and provides clearer information.
@Anonymous, if you want to go with Tim's method, you can brush up on DateDiff.
Here's a primer on using DateDiff for counting down:
@BenFetters, @timl, @mr-dang-MFST,
Thank you for all the great suggestions. It sounds like saving the start and end time and then calculating the elapsed time later may be the best option. If you have any suggestions on how to set this up I would appreciate it. Watching the suggested utube video now.
Hi,
I have somewhat similar problem; however my scenerio is little different. I got my duration fine by using DateDiff. However I am unable to figure out how to add up 2 or more Durations. i.e. if I go on my Break. I am pressing a Button which starts a timer and then once I am back I hit that button again. It Stops the timer and now I have 2 variables for Break Start and Stop which then I use to calculate the duration of my break using DateDiff. Now the tricky part begins. I want to record another break and add the result in previous duration of break to get total time I was on break in whole day. Regardless of how many times I went on break.
I am unable to think it through properly; would really appreciate your advise.
So to sort of briefly explain how I would do that, is I would have a the fields: BreakStarted (Date & Time field), OnBreak (Yes/No field), and a TotalBreakTime (Number field). Then, all you have to do is when you go on break, you set the BreakStarted = Now(), OnBreak = true. Then when you come back from the break, you would set OnBreak = false, and TotalBreakTime = Previous Break Time + Value(DateDiff(BreakStarted,Now(),Minutes)/60) - This way, you just add the 15 minutes of break time you just went on to the previous 15 minutes you already had.
Lastly, when you want to get your total time, you would just subtract the ending time from the start time and then subtract the TotalBreakTime from that.
That is a simplified explanation but if it didn't make any sense or you would like more clarification just let me know!
Kind regards,
Ben Fetters
Hi Ben,
Thanks; this is not exactly what i am looking for but I got my problem sorted. Used Collections store break durations and then in the end Sum them up to get total value.
Thanks.
-------
I have another situation here. I have few people which went on break but then if I go to their record and put them on break on changing / selecting someone else record trigger resets its self. In short app is not keeping its state for individual records. Also I can see variable value of one persons form in a different person. (forms are using same variables though). I think I need to look into Global and local variables if there is any. Any suggestion?
Oh okay, I'm glad your figured out a good solution! And for the other situation, I try throwing some labels on your screen or screens and setting them to the different variables just so you can see things a little more clearly to try to find the problem. Then running through the process and looking for all the different places where the variable is changing or staying the same when it should change? I'm not sure what the problem could be though. But putting labels on the screen always helps me alot as well as testing the app on your phone if you can. Sometimes it works a little differently on the phone. I'll let you know if I think of something else though!
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!
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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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.
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