cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Selected Gallery Item Changes on Patch Function

I have two screens within my app, browseScreen and detailScreen. The first contains a gallery named requestGallery, which references a SharePoint list data source, and the other contains a detail form and several text labels, all referencing the selected item of the requestGallery. The OnSelect property of requestGallery is set to navigate to detailScreen with the selected item.

 

The detail screen also has a couple of buttons which change the value of a column in the selected record of the data source through a Patch function. All of the buttons change the same value, the Status column.

 

The first set of buttons have this set to their OnSelect property:

 

Patch(
    'Rework Data Header',
    First(
        Filter(
            'Rework Data Header',
            ID = requestGallery.Selected.ID
        )
    ),
    {
        Status: "Approved",
        AppRejTime: Now(),
        AppRejBy: userName_
    }
)

This works perfectly, and all objects on the screen update accordingly with no issues. However, the second button has this set to it's OnSelect property:

 

Patch(
    'Rework Data Header',
    First(
        Filter(
            'Rework Data Header',
            ID = requestGallery.Selected.ID
        )
    ),
    {
        Status: "Closed",
        ClosedTime: Now(),
        ClosedBy: userName_,
        ActCost: actCost_input.Text,
        ActTime: actTime_input.Text
    }
)

Upon selecting this button, the correct values are patched to the data source, but it also selects the first item in the requestGallery and all objects switch to reference that. There is no difference in the codes, though, other than the values that are patched to the datasource.

 

Is this a bug, or am I just missing something obvious in my code?

6 REPLIES 6
Anonymous
Not applicable

To add more information, I just tested out setting a Global Variable (selID_) equal to the selected item's ID in the gallery in the OnSelect property of the gallery. I also changed the reference on the Patch function to selID_ instead of the requestGallery.Selected.ID, but the issue remains.

 

It seems as though the Patch function is somehow changing the selected item of the gallery without being told to do so.

v-xida-msft
Community Support
Community Support

Hi @Anonymous ,

Could you please share a bit more about the issue within your app?

Do you mean that the Selected Item within your Gallery would be changed after your Patch formula is executed?

 

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. In order to check if the selected item in your Gallery is changed, you could take a try with the following solution:

Set the TemplateFill property of the Gallery to following:

If(ThisItem.IsSelected, RGBA( 250, 235, 215, 1 ), RGBA(0, 0, 0, 0))

Above formula would highlight the selected item within your Gallery, if the selected item is changed in your Gallery, the Gallery Item color render would also be changed:17.JPG

 

 

As an alternative solution, you could consider save the selected item from your Gallery into a variable, then use the variable within your Patch function.

Set the OnSelect property of the Gallery to following:

Set(CurrentSelectedItem, Gallery1.Selected)

Then modify your formula as below:

Patch(
    'Rework Data Header',
     CurrentSelectedItem,
    {
        Status: "Approved",
        AppRejTime: Now(),
        AppRejBy: userName_
    }
)

If the issue still exists, please consider re-create a new app based on your SP List data source, then try above solution I provided, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

@v-xida-msft Thank you for your reply! I tried your test and confirmed that the Patch function is actually selecting a different entry in the gallery, but just figured out what's causing the problem. I'll start by highlighting the workflow:

 

  1. User selects an item from the requestGallery, which navigates to the detailScreen with a form displaying several fields from the selected item. The screen also has a few labels with Text fields referencing requestGallery.Selected.[x] to highlight important information.
  2. When the status of the request is "New", two buttons are visible to either Patch "Approved" or "Denied" to the status field of the selected entry. Selecting either of these buttons works just fine, and the selected item from the gallery remains selected.
  3. After the request is approved, another button appears to close out the request (patches the status "Closed" to the status field of the selected entry). Upon selection of this button, the correct values are patched to the data source, but all fields on the detailScreen revert to reference the first item in the requestGallery. Using your test, the background color also switches to indicate the selection has changed.

The issue goes away if I remove the SortByColumns function from the items in the requestGallery. Currently, the items in the data source are assigned a value based on their status from 1-4 (New, Approved, Denied, Closed), and that status changes when the button is pressed. If I had to guess, it looks like the gallery selection function in PA has some sort of numerical reference to the item that gets refreshed on Patch. It's strange, though, that this only occurs on the second patch inside the ticket. The first button also changes the status, which would change the sort order in the requestGallery, and there is no issue. I believe this is a bug.

Hi @Anonymous ,

Actually, when the Patch function is executed successfully within your app, your data source would be refreshed automatically, so the Gallery control would also be refreshed.

 

Have you taken a try to save the selected item in your Gallery into a variable? Based on the issue that you mentioned, I think a global variable could fix this issue. Even though, the Gallery is refreshed, the global variable would not be changed.

 

Currently, as an fixed solution, you could remove the SortByColumns function from the Items proeprty of the Gallery. Or you could use the ID column as the Sort column instead of other columns in your SP List data source. Set the Items property of your requestGallery as below:

SortByColumns(
Filter('Rework Data Header', StartsWith(Title, TextSearchBox1.Text)),
"ID",
If(SortDescending1, Descending, Ascending)
)

Please take a try with above solution, then check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

@v-xida-msft  Thanks for your help, but I need the items in the gallery to be sorted by their status, not their ID. The idea is to have the "New" items (which need immediate attention) at the top so they are more visible. I also wouldn't want to save the item as a global variable, because I'd like to be able to change the information. It's alright that the data source refreshes upon a patch, but I still think it's a bug that the reference to the gallery changes.


The solution here will be to set the ID of the selected item to a global variable and then change all of the references in the detailScreen to reference an entry of the data source filtered based off that ID variable, but that seems pretty cumbersome to set every time you need another screen referencing the selected items of a gallery.

AaronAER
Regular Visitor

Agreed, @Anonymous, but I had to do the same. I had a detail screen with multiple dependent and nested forms and galleries, and when I `Patch`ed the main data source, everything would go stupid. So `OnVisible` I store the ID of the selected record, `OnHidden` I set it to blank, and all the lookups on that page are based on the global variable.

 

I agree that it feels like a bug. It's not natural, expected behaviour. It seems like something that could be worked around on the MS side. Maybe even a setting `KeepSelectedOnRefresh` or something like that so it's optional.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (1,771)