Hello, I have a sharepoint list with a Date/Time column (Column 4) and an empty column (Column 5) named "End Time". I have another column next to that named "Status Duration" (Column 5-Column 4).
I am trying to update the last record entered into the list that matches the title in column 1, and enter only the current date and time into the "End Time" column for that record.
On my status dashboard the textbox displaying the status will trigger the entry of the end time OnChange. I created a form, Form1 that contains just a Date/Time field and linked it to the correct datasource.
The original form submitting the data is Form4.
I am trying to use patch but I cannot get the formula correct as you can see below:
Patch('StatusBoardData_HILLIARD_Rev2.0', Form4.LastSubmit.Title, 'StatusBoardData_HILLIARD_Rev2.0'.'End Time'= Text(Now(),DateTimeFormat.ShortDateTime24))
Solved! Go to Solution.
Your time in the list is correct. SharePoint will display dates and times based on the regional settings of the site the list is in. If you have had the regional settings changed, then make sure you are also refreshing the datasource in the designer. It shouldn't make a difference, but I would verify that PowerApps has gathered all the list information properly with a refresh.
Since your duration is a calculated column, you will need to look at the formula for the calculate column in SharePoint to determine/provide what you want for the value. Personally, I would ditch the calculated column and just have a regular numeric column and do the calculation directly in the App.
Well, you've got a couple of things wrong in the formula.
First, if there is an offset based on time zone, then you should be using the TimeZoneOffset function. Also, Value(5) is not necessary...5 is already the Value. You would use Value to convert a Text string to a numeric. Thus, Value("5") would return 5. So again, not needed.
Next, your Notify is referencing a control...not a property. Label8 is a control. You would want to reference the .Text property of the Label - i.e. Label8.Text This kind of thing causes issues at run time.
And finally, you are missing a closing paren in your DateAdd formula.
And as a little extra...it is best not to reference the label, but instead reference what your label derives from. In the context of your formula, my guess is that it references one of the column values of the record you just wrote. So, it should be stated that way in the formula.
With all the above...the formula should be (this version showing your original add to the time):
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Self.LastSubmit.Title),
{'End Time': DateAdd(Now(),Value(5),Hours)}
);
NewForm(Form4);
Notify("Success, " & Self.LastSubmit.Title & " Status Updated!", NotificationType.Success)
This version showing the time zone offset):
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Self.LastSubmit.Title),
{'End Time': DateAdd(Now(), TimeZoneOffset(), Minutes)}
);
NewForm(Form4);
Notify("Success, " & Self.LastSubmit.Title & " Status Updated!", NotificationType.Success)
Hello, I have updated my patch formula and still am not having success.
Patch(
'StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Form4.LastSubmit.Text, 'End Time')
{'End Time': Text(Now(),DateTimeFormat.ShortTime24)}
)
Again, I want the form to find the last record entered into the sharepoint list for the machine that the update was just entered for and then enter the current time in the empty row named "End Time" in the ShortTime24 format for the last record entered.
What are the names of your columns and what type are they? Specifically I am referring to the use of .Text on the LastSubmit...is there a column named "Text" in your list?
Also, you mentioned that your column called "End Time" is an empty column...but what type of column is it? Date or Text?
Hello @RandyHayes , My columns are named "Title", "Status", "Operator", "Time", "End Time", & "Status Duration" in that order.
"Status Duration" is the calculated column based off the "Time" and "End Time" columns.
Title is where the machine # is ex. "EXT 24" or "ACM 40-6"
I have tried the formula below on in my submit button "OnSelect"
If(SubmitForm(Form4_1), Reset(Timer2_4); UpdateContext({varShowPopup1: true}) ; Patch('StatusBoardData_HILLIARD_Rev2.0',LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Form4_1.LastSubmit.Title, 'End Time') {'End Time': Text(Now(),DateTimeFormat.ShortTime24)}); NewForm(Form4_1)
So first, your Submit button should only be SubmitForm(Form4_1)
Always avoid doing anything after the submit form function in your formula as SubmitForm performs asynchronously and trying, for example, to get the LastSubmit, will not be accurate as the SubmitForm has not completed when referenced in the same formula.
Your formula should be in the OnSuccess action of the Form. THIS is where you want to do the actions when the form submits properly.
Also, you are using an IF on a submitform function - That function does not return a value to "if".
So, in your OnSuccess action, the formula should be:
Reset(Timer2_4);
UpdateContext({varShowPopup1: true});
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Self.LastSubmit.Title),
{'End Time': Text(Now(),DateTimeFormat.ShortTime24)}
);
NewForm(Form4_1)
The above assumes again that your End Time column is a TEXT column, not a date column.
@RandyHayes , I've only been using PowerApps for about a month now, these tricks and tips are greatly appreciated.
I made the changes to my submit buttons and form OnSuccess actions.
The code below is now in my OnSuccess Action. I changed the date input from a text string to an actual date becasue the column is formatted as a date.
Reset(Timer2_4); UpdateContext({varShowPopup: true}); Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Form4_1.LastSubmit.Title),
{'End Time': Now()}); NewForm(Form4_1)
When I tested it, it worked perfectly but it entered the time as if it were 5 hours ago. I just had the admin correct the time zone and formatting in our sharepoint site to get 24 hour time. However, it is still inputting the date 5 hours in the past.
In the record below, it as entered 7 minutes after the initial input, instead of showing -5 hours, I want it to show the fractional duration between the two columns i.e. 0.1 hours.
Your time in the list is correct. SharePoint will display dates and times based on the regional settings of the site the list is in. If you have had the regional settings changed, then make sure you are also refreshing the datasource in the designer. It shouldn't make a difference, but I would verify that PowerApps has gathered all the list information properly with a refresh.
Since your duration is a calculated column, you will need to look at the formula for the calculate column in SharePoint to determine/provide what you want for the value. Personally, I would ditch the calculated column and just have a regular numeric column and do the calculation directly in the App.
@RandyHayes , the time is still off after adjusting the sharepoint settings.
I have modified the formula you supplied above to add 5 hours to the time that is input but now I am getting an error.
Old:
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Form4.LastSubmit.Title),
{'End Time': Now()}); NewForm(Form4) ; Notify("Success, "&Label8 &" Status Updated!", NotificationType.Success)
New:
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Form4.LastSubmit.Title),
{'End Time': DateAdd(Now(),Value(5),Hours})); NewForm(Form4) ; Notify("Success, "&Label8 &" Status Updated!", NotificationType.Success)
Well, you've got a couple of things wrong in the formula.
First, if there is an offset based on time zone, then you should be using the TimeZoneOffset function. Also, Value(5) is not necessary...5 is already the Value. You would use Value to convert a Text string to a numeric. Thus, Value("5") would return 5. So again, not needed.
Next, your Notify is referencing a control...not a property. Label8 is a control. You would want to reference the .Text property of the Label - i.e. Label8.Text This kind of thing causes issues at run time.
And finally, you are missing a closing paren in your DateAdd formula.
And as a little extra...it is best not to reference the label, but instead reference what your label derives from. In the context of your formula, my guess is that it references one of the column values of the record you just wrote. So, it should be stated that way in the formula.
With all the above...the formula should be (this version showing your original add to the time):
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Self.LastSubmit.Title),
{'End Time': DateAdd(Now(),Value(5),Hours)}
);
NewForm(Form4);
Notify("Success, " & Self.LastSubmit.Title & " Status Updated!", NotificationType.Success)
This version showing the time zone offset):
Patch('StatusBoardData_HILLIARD_Rev2.0',
LookUp(Sort('StatusBoardData_HILLIARD_Rev2.0', Created, Descending), Title = Self.LastSubmit.Title),
{'End Time': DateAdd(Now(), TimeZoneOffset(), Minutes)}
);
NewForm(Form4);
Notify("Success, " & Self.LastSubmit.Title & " Status Updated!", NotificationType.Success)
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