Hi
I have an app in which the user can choose either to "add feature" or to "edit existing feature", like shown below:
OnSelect property of "Add feature:
Set(g_featID,Blank());
Navigate(Screen2,ScreenTransition.None)
OnSelect property of "Edit Feature"
Set(g_featID,TextInput1.Text);
Navigate(Screen2,ScreenTransition.None)
Upon click, I wanted to use the same canvas-form for the two cases as:
So in the next screen, i implemented like this:
OnVisible property of Screen:
If (IsBlank(g_featID), UpdateContext({l_featMode : "Add"}), UpdateContext({l_featMode : "Edit"}));
UpdateContext({l_status : Blank()});
Refresh(TblFeatures)
Properties of the form on this screen:
DefaultMode: Switch(l_featMode, "Add", FormMode.New, "Edit", FormMode.Edit)
Item: If (Not(IsBlank(g_featID)), LookUp(TblFeatures, FeatureID=g_featID))
With this, I get correct behaviour if I add one feature:
Add feature form
Edit feature form:
But now, if I try to add another record by clicking on "add feature", the form is stuck as "No item to Display":
Note that the first record is added successfully as can also be seen in the excel table.
To me, it looks like a bug!
Will appreciate any support/workaround in this issue.
(unfortunately, I cant export and share app package due to corporate restrictions)
Thanks.
Solved! Go to Solution.
@Anonymous,
I think you made it much more complicated than it needs to be. Powerapps forms usually reference a datatable or a gallery. So normally there is a Datatable or Gallery on the first screen. Forms can either create a record in a datasource, edit one already created or view one (read only). You set the default Form mode using the functions EditForm(Form1), NewForm(Form1) and ViewForm(Form1) before you navigate to the second screen containing the Form. So if the form is on a different screen, you could set up your buttons on your first screen, say Add, Edit . The Add button OnSelect property would be NewForm(Form1), Navigate(Screen2,ScreenTransition.None), The Edit button would be EditForm(Form1),Navigate(Screen2,ScreenTransition.None) Putting the edit button inside the gallery will automatically select the record to edit. The Add button can be outside the gallery because a new form is being created.
On the 2nd screen, there would be an Edit form control. Its Datasource property would be the same as the datasource of the gallery or datatable. Its Item property would be Gallery1.Selected. (The Item property is ignored if the form is in New mode). On the second screen, You would have a button for Submitting the form with the OnSelect property SubmitForm(Form1) in the picture below it is the check mark. The X icon OnSelect property would be ResetForm(Form1);Back(None). so you could go back if you decided not to edit the record. In the OnSuccess property of the form you could put Back(None) and after submitting your property, the app would navigate back to the first screen and your new or edited item would be displayed in the gallery or datatable. I hope this helps. In the example below, I edited Adrian's record by adding Unknown in the Status box. After clicking the check mark, The form navigated back to the Gallery screen and the new status is shown.
@Anonymous,
I think you made it much more complicated than it needs to be. Powerapps forms usually reference a datatable or a gallery. So normally there is a Datatable or Gallery on the first screen. Forms can either create a record in a datasource, edit one already created or view one (read only). You set the default Form mode using the functions EditForm(Form1), NewForm(Form1) and ViewForm(Form1) before you navigate to the second screen containing the Form. So if the form is on a different screen, you could set up your buttons on your first screen, say Add, Edit . The Add button OnSelect property would be NewForm(Form1), Navigate(Screen2,ScreenTransition.None), The Edit button would be EditForm(Form1),Navigate(Screen2,ScreenTransition.None) Putting the edit button inside the gallery will automatically select the record to edit. The Add button can be outside the gallery because a new form is being created.
On the 2nd screen, there would be an Edit form control. Its Datasource property would be the same as the datasource of the gallery or datatable. Its Item property would be Gallery1.Selected. (The Item property is ignored if the form is in New mode). On the second screen, You would have a button for Submitting the form with the OnSelect property SubmitForm(Form1) in the picture below it is the check mark. The X icon OnSelect property would be ResetForm(Form1);Back(None). so you could go back if you decided not to edit the record. In the OnSuccess property of the form you could put Back(None) and after submitting your property, the app would navigate back to the first screen and your new or edited item would be displayed in the gallery or datatable. I hope this helps. In the example below, I edited Adrian's record by adding Unknown in the Status box. After clicking the check mark, The form navigated back to the Gallery screen and the new status is shown.
Hi @Anonymous
actually @Drrickryp, was right about about complicating simple things!
since PowerApps started using DisplayMode property i started using only a single form for both editing and viewing.
so here's what i suggest you do:
try it out and let me know if it is successfull.
regards,
Mohammad
@Drrickryp, Thanks for introducing me to EditForm, NewForm and ViewForm functions.
and saving me from extra complexity - appreciate it.
@mokhawaja The step 4 shared by you was quite useful to improve my actual app's behavior...
Thanks for step by step details
thanks @Anonymous, glad you solved your issue!!
I was totally stumped on this one! Finally came across this post.
I'd had Select(Parent) where I should have had ViewForm(frmRequest_1). No matter what I did, my form was always in Edit mode when I selected it from the gallery. When I used ViewForm...it took care of things! Thanks ever and ever so much!
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