Hi,
I have two lists - main list and related list. I have created a related field in the second list called IDRefSec which automatically gets populated with the ID from the main list.
When I open the record, I use the following code to locate the related record (in the Items property):
What I am now trying to do is patch the current open related record. In my other screens, I reference the ID of the selected gallery, however because this record is not opened from a Gallery, I am not sure how to reference it, my code is as follows:
// With varSecRec collection
// Check if related record exists. If it does not, then patch as a new record
ClearCollect(
varSecRec,
Sort(
NewEmployeeSecurity,
ID,
Descending
)
);
If(
IsBlank(
LookUp(
varSecRec,
(IDRefSec = varCurrRecord)
)
),
Patch(
NewEmployeeSecurity,
Defaults(NewEmployeeSecurity),
frmSecurityDetails.Updates;
),
Patch(
NewEmployeeSecurity,
{ID = <<<<CURRENT OPEN RECORD BEING EDITED>>>>},
frmSecurityDetails.Updates
)
);
Set(
varSaveStatus,
"Saved"
)
Its the second patch command I am trying to get working.
Any help is always greatly appreciated.
Cheers,
Geoff.
Solved! Go to Solution.
EditForms support comboboxes as well as all other controls.
I would advise making sure you have the datacards set up properly and just let PowerApps do what it does best with EditForms and avoid any of the extra work of the formula you're trying to build.
Since you are trying to Patch the Updates property of the Form, then that would assume you already have the comboboxes working properly for your comboboxes.
In which case, doing a SubmitForm(frmSecurityDetails) is all you need.
When you skip the submit and try to Patch, you lose the features of the form, and you introduce errors in your app or more work to be done. One case in point...you are setting a varSaveStatus to "Saved", how do you know it is saved? What if the Patch fails? With the SubmitForm, you get a OnSuccess action. In that OnSuccess you would put your setting of the variable, then you know it is saved.
If you do a NewForm(frmSecurityDetails) when you are creating a new record, then the SubmitForm will handle creating one. If you are doing an EditForm(frmSecurityDetails) then again, the SubmitForm will handle all the work for you.
You appear to be doing this in a Form.
My first question would be, why are you not just doing a SubmitForm on the form?
However, since it is a Form, you will have set the Item property to some record. It is that record that will have the ID of the current record.
But as mentioned, what you are doing in your formula, the SubmitForm will take care of for you.
Hi Drrickryp,
I don't think that will work, what happens is a record is selected from the main gallery, and it opens a new screen which has two forms on it. The from from the gallery is read only, while the form from the related list is in edit mode. So if the form currently being edited is saved, what happens if that was not the last record patched?
Cheers,
Geoff.
Hi Randy,
Thanks for your reply, the related form has multiple Combo boxes on it so I will need to use the patch to get this working.
Cheers,
Geoff.
EditForms support comboboxes as well as all other controls.
I would advise making sure you have the datacards set up properly and just let PowerApps do what it does best with EditForms and avoid any of the extra work of the formula you're trying to build.
Since you are trying to Patch the Updates property of the Form, then that would assume you already have the comboboxes working properly for your comboboxes.
In which case, doing a SubmitForm(frmSecurityDetails) is all you need.
When you skip the submit and try to Patch, you lose the features of the form, and you introduce errors in your app or more work to be done. One case in point...you are setting a varSaveStatus to "Saved", how do you know it is saved? What if the Patch fails? With the SubmitForm, you get a OnSuccess action. In that OnSuccess you would put your setting of the variable, then you know it is saved.
If you do a NewForm(frmSecurityDetails) when you are creating a new record, then the SubmitForm will handle creating one. If you are doing an EditForm(frmSecurityDetails) then again, the SubmitForm will handle all the work for you.
Hi Randy,
Can you let me know what you mean by 'I would advise making sure you have the datacards set up properly'? What do I need to do to set them up properly? In all of my forms, the Comboboxes never saved their values back to SharePoint after I used a Submit form, so I used form updates (to save the non combo boxes) and just patched the Comboboxes manually. Any pointers here would be greatly appreciated.
Cheers,
Geoff.
So, the thing is, you are using the .Updates property of the form. If that is accurate and gives you the proper values you need, then you are already accounting for the comboboxes or anything else in your form. So the SubmitForm would do what you need. I did not see in your formula where you were patching comboboxes back to the list.
Comboboxes and other controls are used all the time. If the source of your information for the control is from your datasource list, then you can simply change the control type in the field editor. If it is coming from another location, then you simply need to change the Items property of the control. The only key to getting everything connected is to make sure the Update is providing the value you want for your list (the same thing you have in any patch formula you are doing for them on the side) and getting the Default items properties set properly to display any value in an existing records.
There is a WIDE variety of scenarios so it is hard to just pinpoint one and have it even remotely meaningful to your scenario. If you have a specific combobox/field type that you have had difficulty with, I'd be happy to expand on the mechanics of it for you as I can assure you, using the features of the EditForm will significantly reduce your formulas, work, errors and headaches.
I have a video that covers all of the mechanics of EditForms (and a lot more then many know about using them). It's a long video, but covers all the basics of the form in depth. I don't cover specific controls in the form like putting comboboxes in specially (I have a partially finished video on that one). Perhaps some scenarios from you will energize me to finish that video.
Ok, I understand the relationship between the DataCard Update property and the Combobox DefaultSelectedItems property now. For anyone else out there, the ComboBoxes and Dropdown lists do not work like MS Access (where values automatically get written back to data tables), they have to be configured manually:
Configure DataCard Update property to write back to SharePoint field:
If all of your Comboboxes values disappear after a form submit (but the normal fields still retain their values), then you can get the Comboboxes to retain their values by updating the ComboBox DefaultSelectedItems property:
Cheers,
Geoff.
Hi Randy, big thanks for your help here. I think we were both typing at the same time. You are correct - I should have configured my DataCards / ComboBoxes correctly, then the patching on my other forms would have been unnecessary. I keep relating Comboboxes back to MS access, and I now see why we have DataCards (due to different data sources) so configuring Data Cards and ComboBoxes makes sense now. I will watch your video later today. I have a lot of work to do unpatching and setting up data cards properly in all of the other forms in my app.
Cheers,
Geoff.
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