I am getting an error upon submission. This is my submit button outside of the gallery orAll(
Gallery2.AllItems,
If(
!IsBlank(Radio4.Selected.Value),
Patch(
'DE Radio',
Defaults('DE Radio'),
{
Title:Namee,
Answer: Radio4.Selected.Value,
Name_:User().FullName,
Date:Today()
}
)
)
); I only want the selected radio buttons to be submitted. Namee is a text label in the gallery and its text is ThisItem.Namee, which has the name of each item I want to patch. I am getting an error that says that title is required but I have that. Additionally it is patching random radio buttons. When I do Title:Title it picks another text label ThisItem.Area why does it choose this as the title?
Solved! Go to Solution.
@Anonymous
So I was able to get closer to your situation in a little test app I put together. I DO see that there is some unusual behavior wherein the value of the first Radio control is being "ghosted" for the other items. I've not seen this behavior with that control before and wonder if it is a temporary bug or if it is some other issue.
So, let's revisit the formula then on your Submit button. Change to this and I believe your issue will be solved:
With({usrFull: User().FullName},
ForAll(
Filter(Gallery2.AllItems, !IsBlank(Radio)),
Patch('DE Radio',
Defaults('DE Radio'),
{
Title:Namee,
Answer: Radio,
Name_:usrFull,
Date:Today()
}
)
)
)
Since you are patching the Radio column on the OnChange, the underlying record will have the correct value and you can use that in the formula instead.
@Anonymous
Yes, but the issue I see with that approach is that you are going to be generating many many new records into your list and you will quickly get to the point where you run into delegation issues and record limits.
A separate list with the record ID, the user email and the current radio value would lessen that issue.
@Anonymous
So the only reason then you are having to close and reopen is because you are using a collection that is only loading in the OnStart.
Change your OnChange of the Radio to:
Patch(GUATResponses,
Coalesce(LookUp(GUATResponses, Title=vUserMail && GUATListID=Text(ThisItem.C1)),
Defaults(GUATResponses)
),
{Title: vUserMail, GUATListID: ThisItem.C1, RadioValue: Radio4.Selected.Value}
);
UpdateIf(collGUATMasterData, C1=ThisItem.C1, {C3:Self.Selected.Value})
That will update your collection at the same time.
@Anonymous
Let's first clean up the formula a little - since you're only working on non-blank radio controls, set your formula to this:
With({usrFull: User().FullName},
ForAll(
Filter(Gallery2.AllItems, !IsBlank(Radio4.Selected.Value)),
Patch('DE Radio',
Defaults('DE Radio'),
{
Title:Namee,
Answer: Radio4.Selected.Value,
Name_:usrFull,
Date:Today()
}
)
)
)
(also - User().FullName is performance costly, so here we just have it as a scope variable and hit it once)
Next question, this is all assuming that 'DE Radio' is part of your Items property for Gallery2. If so, then Namee is included and should be available and valid for your Patch.
See if this is helpful for you.
Yes, it is in my gallery. However, this patch statement didn't work it patched 30 records when I only selected 3 records and there are 46 total. The first button I hit works and it defaulted the other 27 to works why does it do this? @RandyHayes
This is my default for the radio ThisItem.Radio this is my items for the radio RadioItems.Value. This is what I have for onchange for the radio Patch(GUAT,ThisItem,{Radio:Radio4.SelectedText.Value}). I suspect the error is coming from one of these because before I added this it patched perfectly. @RandyHayes
@Anonymous
So am I correct that you are trying to Patch another list if a user changes the Radio control, and that you are also trying to Patch another list based on items that have values?
One thing you might want to look at doing is to change the OnChange formula to this:
If(!(ThisItem.Radio = Radio4.Selected.Value),
Patch(GUAT, ThisItem, {Radio: Radio4.Selected.Value})
)
Two things
1) There is no SelectedText property being used - it is a deprecated property...avoid using it.
2) It checks before patching. That way you are not constantly patching back to the datasource.
The way the app will work is that they will go in select some radio buttons submit then leave and continue the next time they open the app. So i need their previous responses to stay so they know what they have already completed. Then when the submit button is hit I want everything submitted by that user to overwrite and update with their new responses. This is the gallery, @RandyHayes
When submitting it looks like it is defaulting the first response to all the blank ones and they are all coming through. @RandyHayes Everything was submitting until made the radio buttons stick when filtering. @
@Anonymous
Could you clarify "I want everything submitted by that user to overwrite and update with their new responses."
If you are saving all through the process, then there is nothing to overwrite and update. Unless, this is where the 'DE Radio' list comes into play?
I am getting that your Gallery is based on the GUAT list and that you are updating that list as users change the Radio values.
And, when you then "submit", you are then creating new records in the 'DE Radio' list for each item that has a value in the Radio control in the Gallery.
- Your Gallery (based off of GUAT) has a Radio control in it that has a Default set to ThisItem.Radio
- Namee is the second column of your gallery and is shown in the gallery with a label and a Text property of ThisItem.Namee
Please confirm all of the above and then let's explore the issues.
That is where DE Radio comes into play. The patch statement sends their responses of works, issues, fails. I already have the statement in my submit button that removes their previous responses and updates them with the new ones and the old ones since I want those to be defaulted. I want the default of the radio button to be what they previously selected so they dont have to reselect it when they open the app. Currently, when someone else opens the app they can see the answers I submitted which should not happen because the app should only be pulling the previous answers from that specific user. And yes both of the bullet points you listed are correct. The mains things I need - 1. When the user reloads the app to have radio buttons default to what they have already submitted 2. Only submit the radio buttons that they have checked with works/issues/fails @RandyHayes
I have this exact functionality working with another app that uses checkboxes instead of radiobuttons so I can show the code for that if I'm not explaining it enough
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