I have a Gallery with info that has been collected via a SQL view. The view contains the key fields for looking up the specific record in the source SQL table. I want to give the user the option of updating a field in that record. The gallery rows contain the current and new values of that field, with the new value defaulted to the current value. The user will scroll down and enter values in the New value field for the desired gallery rows. Then the user will press an Update Button above the Gallery. On Select for the Update Button, PowerApps should select the rows where new values were entered and for each one, retrieve the target row using the two key fields and update the value in that row.
I am thinking that, since I have the key values which uniquely identify the row to be updated, I don't need to use filter or lookup for specifying the update row (2nd Patch parameter). I should be able to directly link to the target record in the source table.
Source Data (record to be updated)
Table A
Key fields are Fld1 and Fld2
Field to be updated is UpdValue
Gallery named myGallery, with Rows containing
txtFld1 from a.Fld1
txtFld2 from a.Fld2
txtCurValue from a.UpdValue
txtNewValue - input value
On Select action for the Update Button
ForALL(Filter(myGallery.AllItems,txtCurValue.Text<>txtNewValue.Text),
Patch(
'A',
Fld1=txtFld1.Text && Fld2=txtFld2.Text,
{UpdValue:txtNewValue.Text})
)
Solved! Go to Solution.
Probably one of the worst examples that they have in the docs!! That ForAll is not used properly in that example and will lead to horrible performance issues.
In your current OnSelect formula, your syntax does not appear to be correct.
Your formula should be the following:
Patch(A,
ForAll(
Filter(myGallery.AllItems,
txtCurValue.Text <> txtNewValue.Text &&
Fld1 = txtFld1.Text &&
Fld2=txtFld2.Text
),
{ID: ID,
UpdValue:txtNewValue.Text
}
)
)
What is important to include is the ID (primary key) of your record if you wish to actually update a record. If you do not provide that, then your Patch will create a new record.
As @EddieE mentioned...share any Formula that you are getting an error on.
I hope this is helpful for you.
A quicker way is to use a Patch( ... ForAll ( .. ) ) rather than a ForAll( .. Patch(..)). See here for more explanation from @RandyHayes
For your situation, you need to make sure that the Gallery contains all the fields/columns from you SQL view (not a cutdown version) and then you should be able to do this on the Update button
Patch(
'A',
ForAll(
Filter(
myGallery.AllItems,
txtCurValue.Text <> txtNewValue.Text
),
{
Fld1: Fld1,
Fld2: Fld2,
UpdValue: txtNewValue.Text
}
)
)
I'm used to using SharePoint and not SQL but this should work. The reason for including Fld1 and Fld2 in your record update is so that PowerApps knows which record to work on. That link explains this a little more.
Thank you, @EddieE . I'm still trying to getting it to work. The example in https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/functions/function-patch uses ForAll like my original example, at the outer level. From what I can tell from the documentation, Patch requires three parameters and your example uses ForAll as the 2nd and final parameter, as does the solution by @RandyHayes . PowerApps is telling me I have a patch parameter problem. Perhaps there's some magic that pulls the 2nd and 3rd Patch parameter from the ForAll but at this point, what I have (which I think corresponds to your examples) is syntactically incorrect.
Could you please post the code you are getting the error on, I may be able to spot the error.
Probably one of the worst examples that they have in the docs!! That ForAll is not used properly in that example and will lead to horrible performance issues.
In your current OnSelect formula, your syntax does not appear to be correct.
Your formula should be the following:
Patch(A,
ForAll(
Filter(myGallery.AllItems,
txtCurValue.Text <> txtNewValue.Text &&
Fld1 = txtFld1.Text &&
Fld2=txtFld2.Text
),
{ID: ID,
UpdValue:txtNewValue.Text
}
)
)
What is important to include is the ID (primary key) of your record if you wish to actually update a record. If you do not provide that, then your Patch will create a new record.
As @EddieE mentioned...share any Formula that you are getting an error on.
I hope this is helpful for you.
Thank you, @RandyHayes and @EddieE . I think we're getting close.
Here's what I have right now:
//Patch(
//'A',
ForAll(
Filter(
SiteGallery.AllItems,
txtUpdateCur.Text<>txtUpdateNew.Text && SD_ID=txtSD_Id.Text
),
{
SD_ID:txtSD_Id.Text,
SiteGenderRestrictionCode:txtUpdateNew.Text
}
)
//)
This has the Patch commented out, and it shows the syntax as being correct. With all uncommented, it says there are invalid arguments. When I hover over the ForAll, it says it's a table and expects it to be a record.
What is the column type for SD_ID in your table? I assume that is the primary key?
When the patch complains about expecting a record and not a table, that means that there is an issue with the schema of the table returned from the ForAll. So, check that the types are correct.
@akharns
I’m fairly sure you don’t need this inside your filter
SD_ID=txtSD_Id.Text
Then inside your record / {…} change this
SD_ID:txtSD_Id.Text
to this
SD_ID: SD_ID
As @RandyHayes says, there’s a data type mismatch somewhere but I this these changes should sort it out
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