Hi!
I have 2 galleries within one bigger gallery, and I want to patch them but the code is not running even though it is not showing any errors.
A typical patch for my gallery would be
ForAll(Gallery.AllItems, Patch(SPSource, Defaults(SPSource), {ColumnHeader: "Test"}));
So in my nested gallery case, it would be
ForAll(ParentGal.AllItems, ForAll(ChildGal01.AllItems, Patch(SPSource, Defaults(SPSource), {ColumnHeader: "Test"})));
**This code is only has 1 subgallery for ease of solution, but is meant to have like the scenario suggested 2 subgalleries.
This person has a similar issue to mine but the replies were not relevant. Is something wrong with my logic?
Hello @mayalghamdi,
I haven't tested your solution but I do Imagin that there are som issues for power apps te resolve what instance of gallery one you are targeting.
Try this instead (Sudo-function, not tested):
ForAll(
ParentGal.AllItems,
ForAll(
Filter(
YourCollection1,
YourID = ThisRecord.ID),
Patch(
SPSource,
Defaults(SPSource),
{ColumnHeader: "Test"}
)
);
ForAll(
Filter(
YourCollection2,
YourID = ThisRecord.ID),
Patch(
SPSource,
Defaults(SPSource),
{ColumnHeader: "Test"}
)
)
);
If you are wondering where "ThisRecord" comes from, this is a default variable born when doing a ForAll.
Hope this helps!
Please mark this a the Solution and provide som Kudos, so i know I'm helping 🙂.
Hey Daniel!
thank you so much for sharing! And yes there are issues with PowerApps recognizing which gallery youre targeting in a situation like this, hence me proposing the .AllItems property. I want to test out your solution but I am not sure what the collections are. Are you suggesting I collect each smaller gallery in a collection first?
Hello @mayalghamdi,
For optimal performance we normally do a ClearCollect() in visible of the screen or when the app starts, App OnStart. But no I'm not suggesting collecting the smaller galleries.
This follows the following syntax:
ClearCollect(
colYourCollectionNamn,
YourDatasource
)
If you havn't done this it's a performance improvment suggestion. Just keep the 2000 row limit in mind.
But never the less, in my mind you have at least two datasources:
In the Parent gallery you have Datasource A and in the child you have Datasource B. This means your source for the child gallery should look like this:
Filter(
Datasource B,
ParentID = ThisItem.ID // This will filter the datasource to display related rows
)
Otherwise you might have a self referencing lookup, in any case you need to filter in order to disply only related rows in the child gallery.
The same applyes when you need to patch in a ForAll().
Please include some more info if I have come to the wrong conclusion.
Please mark this as the Solution and provide som Kudos, so i know I'm helping 🙂.
@mayalghamdi could you provide a screenshot of your app and describe your datasources so I get a better understanding for what each gallery are used for.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Hey,
I actually only have one source (SPSource = Sharepoint list). My app looks like this
Parent Gallery: no other records than the child galleries
Child Gallery 01: Revenue forecast value 01, Revenue forecast value 02 (for forecast possibility of 50%)
Child Gallery 02: Revenue forecast value 01, Revenue forecast value 02 (for forecast possibility of 90%)
My singular SP list's headers are: Revenue forecast value 01, Revenue forecast value 02, Possibility.
So my expected save methodology should save both galleries using defaults, meaning it saves the first child gallery values using defaults in the sub patch code for Child Gallery 01, patching the revenue values in the perspective column headers in the SP, and patching a text of "Probability 50%". Then does the same thing, saving Child Gallery 02, patching same revenue forecast values, except here its patching a text of "Probability 90%".
my code now
Please let me know if I cleared it any better. 🙂
Hi Power Ranger, please see in the reply I just posted before this one. I have screenshots and all. Let me know if you need any thing else.
Thanks for sharing, I will need to make a test at my end.
Could you also share what the source is of all your galleries please?
Then I'm sure we will solve this issue.
Hi! My galleries are just a sequence of periods.
Child galleries' items:
ForAll(Sequence(PeriodCount.Selected.Value, 0, 1), DateAdd(DateValue(StartingPeriod.Selected.Value), Value, Months))
*PeriodCount is dropdown for how many periods (3 months, 6 months, etc)
*StartingPeriod is date to start with
Parent gallery's items
Dropdown1.SelectedItems
Regards,
May
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