The issue was not yet resolved with the below solution that you guys provided. But it was helpful
I need to submit the request with the submit button click along with the collection.
I have to save the collection information to a separate list with the reference ParentListID.
The first list will have the submitted main request and the second list will have the reference ParentListID and the Qty.
I am using the following formula on Submit.OnSelect
SubmitForm(form1);ForAll(Collection1,Patch('Quantity_List',Defaults('Quantity _List'),{ProductID:EditForm1.LastSubmit.ID,Item ID:ItemID,Quantity:Qty}))
it says patch has some invalid arguments. Please help me with this
Hi Naresh,
Your LastSubmit construct looks wrong - you've got
SubmitForm(form1) but EditForm1.LastSubmit
If you want to reference the form submitted it should be form1.LastSubmit, so;
SubmitForm(form1); ForAll(Collection1,Patch('Quantity_List',Defaults('Quantity _List'),
{ProductID: form1.LastSubmit.ID}))
I purposefully left out the other columns in your patch - I'd suggest you first make sure this works, then add the other columns back in.
As I said in your other post though - be aware that by not using the OnSuccess property of the form, you're assuming everything went off successfully. If it doesn't, you might get submission errors or patch errors or you might capture orphaned data to the source.
Hope this helps 🙂
RT
In shows Two errors
1.Patch has some invalid arguments
2.ProductID column doesn't exists.
Hi Naresh,
Either the column you entered doesn't exist, or it exists under a different name.
Depending on how the list and the column were created, it could be either, so if it's not immediately obvious to you what the problem is, here's a few things to check;
First, to test the LastSubmit function - create a new list manually through SharePoint with only two columns - the default Title column you get when creating a new list and add a single-line text column called ProductID. (Do not rename the Title Column, create an additional column called ProductID)
Update your patch to the new table and column label and see if it works.
If it does, a few things to check with your original Table;
1: Start by replacing ProductID with Title in your patch statement.
This is just a guess 🙂
If this does not work;
2: Check your original source through powerapps using a simple text label on a screen with a Text property function like First('Quantity Master'). and after the . wait for the field prompts to see if ProductID is listed there. If it isn't, then either it's not there, or it's there under a different name.
Hope this helps
RT
you are Awesome...
I have changed the title field to the ProductID. But still, PowerApps taking it as a title field.
Now it works fine.
How to show up all this information in the detailed screen with the child items selected(stored in a collection).
and also child items should be deleted Once I delete the parent request.
Please help me with this
Hi Naresh,
Glad to hear you got it working 🙂
Not sure what you mean by
"How to show up all this information in the detailed screen with the child items selected(stored in a collection)."
But if the detail screen is an edit form for an item from the first source, then you can add any control to the form that references lookups from the second source using the ProductID (or Title as the case may be) reference.
So, if someone selects a record from a gallery which takes them to the detail form for the primary source, you can add controls to the details form that reference the secondary source using ProductID=gallery.selected.ID
Removing is basically the same in reverse - if someone wants to remove the parent, first go and do a RemoveIf() on the second source using the ProductID reference, then remove the primary source using the ID reference.
Hope this makes sense, a bit hard to do without the example in front of me 🙂
If not, take some screenshots that include the screen and formulas you're using and I can try make it more specific
Kind regards,
RT
OK then I will go step by step. Hope you can help me with this.
Thanks once again for being so supportive.
After submission the screen will move to the browsergallery(dashboard screen). From the gallery it will take to the detail screen
here I can see only the parent information how to link with the child data and display here(Child data was stored in the collection)
I want the child data to be display in the gallery.
Ok, so assuming you have a 1-to-many relationship between a parent record and related children, then you just need to filter the child collection by the currently selected/displayed parent record ID.
So if the top piece is a display form for the parent record, presumably the item it's displaying is whatever was selected on a previous screen gallery;
Displayform Item:
BrowseGallery.Selected
Your bottom piece would then be a filter of your children related to the same parent record, be they in a collection or other source, as follows
ChildGallery Items:
Filter(childCollection, ProductID=BrowseGallery.Selected.ID)
Obviously I don't know the precise names of your data sources, controls or columns, just make sure you change the above to reflect them accurately 🙂
Hope this helps!
RT
ChildGallery Items:
Filter(childCollection, ProductID=BrowseGallery.Selected.ID)
It means the Childcollection should have the Product ID value init right?
But we have patched the collections using the product ID So, We dont have the product ID in the Childcollection.
This is the formula I have used to patch the collection data
SubmitForm(EditForm1);
ForAll(cQuantity,Patch('Quantity master',Defaults('Quantity master'),{Title:EditForm1.LastSubmit.ID,Item_x0020_ID:ItemID,Quantity:Qty}));
So, how can I bring the product ID to get it filtered here?
Sorry, I thought the Title column was your ProductID column?
Not sure of the exact column names or structure of your tables, but if you're patching 'Quantity Master' with the LastSubmit.ID of EditForm1, then I'm guessing EditForm1 is updating your primary datasource and 'Quantity Master' is your secondary - therefore if you wanted to filter 'Quantity Master' by all items relating to the primary data source, you would do the following;
Filter('Quantity Master', Title=[primary datasource table here].ID)
I posted a response here which talks about primary and foreign keys, there's a picture there that might help.
Kind regards,
RT
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