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

Detail Record Card Switches After Use of "Patch"

Accept DateAccept Date

 

 

I am experiencing a strange behavior.  On my Edit Detail card, I have added controls to populate a date in SharePoint Online.

The user must choose a toggle button which make the "Accept" button enabled.  Using the "On Select" property enables the date to be saved to the data source.  The date is saved successully, however after I patch the record the user detail field goes the first record instead of staying on the record that is currently selected.

 

Patch(ActiveUsers,First(Filter(ActiveUsers,BrowseGallery1.Selected.DistinguishedName = DistinguishedName)), {MoveDate: MoveDatePicker.SelectedDate + Time(Value(HourDropdown.Selected.Value), Value(MinuteDropdown.Selected.Value), 0)})

 

I cant determine how it is possible but the only thing differrent is the addition of the Patch that is executed.  Anyone have ideas on why my detail card switches from the current record to the first record?  What might be a workaround to keep the current record the current record?

 

Thank you,

 

 

W.

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

I found a solution.  It is an extension of JoshHoughton's idea.  I've been testing this for over an hour, trying to come up with scenarios where this would fail and could not produce one.  JoushHoughton passed a record as a context variable and used it in the Item on the detail form. If you updated the record in the background using patch, it could not be reflected in the detail form.

 

Passing a unique identifier for the record and then utilizing it to obtain the actual record, it works without fail.  After the patch, the form stays with the current record and the updates are reflected in the form.

 

NextArrow

OnSelect = Navigate(DetailScreen1, ScreenTransition.None, {CustomRecordSelected: BrowseGallery1.Selected.DistinguishedName})

 

DetailForm1

Item = First(Filter(ActiveUsers,CustomRecordSelected = DistinguishedName))

 

BrowseGallery1.Selected.DistinguishedName uniquely identifes this record and is stored in CustomRecordSelected

 

See the illustrations below

 

I hope this helps other.

 

Thanks to JoshuaHoughton.  His initial idea got this ball rolling.

 

 

W.

 

 

 

Overcome Record Change Bug Part 1Overcome Record Change Bug Part 1 

Overcome Record Change Bug Part 2Overcome Record Change Bug Part 2

 

 

 

 

View solution in original post

12 REPLIES 12
v-yamao-msft
Community Support
Community Support

Hi wedwards,

 

I’d like to know more details about “however after I patch the record the user detail field goes the first record instead of staying on the record that is currently selected”.


Could you show me more details about this situation?

 

I have created an app based on your description, the function I am using on my side is:

Patch(ProjectEmail,First(Filter(ProjectEmail,Title=BrowseGallery1.Selected.Title)),{h4kv: DateValue1.SelectedDate+Time(Value(HourValue1.Selected.Value),Value(MinuteValue1.Selected.Value),0)})


When I click the button to patch the date time to data source, it saved properly and seems that I don’t get the issue “the user detail field goes the first record instead of staying on the record that is currently selected”.


The date time field displays properly on all of the three screens, BrowseGallery, DisplayScreen, EditScreen.

 

Could you please try it again with the function and feel free reply if you are still having the issue.

 

Best regards,
Mabel Mao

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

 

>> Could you show me more details about this situation?

 

InactiveInactiveActiveActiveDetailCardDetailCard

(this changes from the current record to the data from record number one, after I choose "Accept")

 

 

I have a BrowserGallery and a DetailScreen and have removed (deleted) the edit screen and hidden the edit icon on the edit screen because I did not want the records edited by the users, except for the date field.  The date is the only user modifiable interface.

 

The user can modify the date but can only accept the date after first turning the toggle button on, which enables the "Accept" button.  If the toggle button is turned off, the "Accept" button is disabled.

 

The purpose is to ensure the user must actively consent and "Accept" the date.  This keeps me from having to put up a dialog, asking "Are you sure you want to accept this date?" It wasn’t accidentally accepted.

  

Once the user clicks "Accept" using the "OnSelect" property, I patch the record on SharePoint.  I see the progress dots go across the screen for a few seconds, the screen flashes momentarily with the same user record.

A few seconds later,  ( From the appearance, after the patch has completed) the screen begins to update but instead of showing the same record, the details for record number one show up.

 

Interestingly, the correct record is updated but it is confusing to see the details for record one appear after updating another.

 

Patch(ActiveUsers,First(Filter(ActiveUsers,DistinguishedName=BrowseGallery1.Selected.DistinguishedName)), { MoveDate: MoveDate.SelectedDate + Time(Value(HourDropdown.Selected.Value), Value(MinuteDropdown.Selected.Value), 0)})

 

My Patch statement appears to be identical (in form) to yours.  I initially had the filter condition as BrowseGallery1.Selected.DistinguishedName=DistinguishedName but just in case (I didn’t see how it would make a difference)  I swapped the order to DistinguishedName=BrowseGallery1.Selected.DistinguishedName

 

Thank you,

 

 

W.

Anonymous
Not applicable

After looking for more information on this issue I found another user who is experiencing the same behavior.

 

https://powerusers.microsoft.com/t5/PowerApps-Forum/SubmitForm-command-changes-Gallery-Selected-item...

 

User JoshHoughton provided a workaround (see above link).  The workaround does work, however the Calendar control on the page visibly stays the same my the view (it should) but something changed in the background because the text that matches the selected calendar control changed to reflect todays date which is the default value of the calendar.

 

 

 

 

Date doesnt match after updateDate doesnt match after update

 

 

This is my TEXT property for the selected label.

 

Text(ChangeDatePicker.SelectedDate + Time(Value(HourDropdown.Selected.Value), Value(MinuteDropdown.Selected.Value), 0), "[$-en-US]ddd, dd mmm yyy, hh:mm am/pm")

 

I would like this to execute without a workaround but in the interim, would someone have an idea of what I might do to ensure the text display matches the date chosen, even after the update?

 

Thank you,

 

 

W.

 

 

I think I'm having the same or very similar issues when using Patch(). I intend to make a new forum post on here describing the issue, although as my situation is a bit complex it'll take me awhile to write out a proper explanation. Was just wondering, before I type it all out, did you find any new info/workarounds?

Anonymous
Not applicable

Unfortunately, I have not.  I spend most of the day yesterday trying to come up up with a solution.  I was willing to entertain oddball solutions.  If you navigate to the previous screen and reselect the record, it is up to date. 

 

Knowing this, I tried a hostile exercise of programmatically navigating back and redisplaying the card but (unless I did something wrong) it didnt work.  It appears that Patch is Asynchronous, so placing a command directly after the patch can (and in my case does) occur before the patch completes.

 

https://powerusers.microsoft.com/t5/PowerApps-Forum/SubmitForm-command-changes-Gallery-Selected-item...

 

Currently the best workaround is the post by JoshHoughton on the above link.  The solution is lets say 99% effective.  It keeps you on the selected record but something is happening after the patch in the background that appears to be causing a reset of of the edit form or something like a reset.  I placed a refresh icon on the page (as a test) and performed a Refresh (after the patch) and so the form should have updated with the most recent data that was patched into the SharePoint list but that didnt happen. 

 

Sadly, the customized card that has controls whose valuest do not come from the parent are not updated.  They maintain the values they had prior to the patch.  This is why I say that JoshHoughton workaround is 99% effective.

 

 

W.

 

Anonymous
Not applicable

I found a solution.  It is an extension of JoshHoughton's idea.  I've been testing this for over an hour, trying to come up with scenarios where this would fail and could not produce one.  JoushHoughton passed a record as a context variable and used it in the Item on the detail form. If you updated the record in the background using patch, it could not be reflected in the detail form.

 

Passing a unique identifier for the record and then utilizing it to obtain the actual record, it works without fail.  After the patch, the form stays with the current record and the updates are reflected in the form.

 

NextArrow

OnSelect = Navigate(DetailScreen1, ScreenTransition.None, {CustomRecordSelected: BrowseGallery1.Selected.DistinguishedName})

 

DetailForm1

Item = First(Filter(ActiveUsers,CustomRecordSelected = DistinguishedName))

 

BrowseGallery1.Selected.DistinguishedName uniquely identifes this record and is stored in CustomRecordSelected

 

See the illustrations below

 

I hope this helps other.

 

Thanks to JoshuaHoughton.  His initial idea got this ball rolling.

 

 

W.

 

 

 

Overcome Record Change Bug Part 1Overcome Record Change Bug Part 1 

Overcome Record Change Bug Part 2Overcome Record Change Bug Part 2

 

 

 

 

Thanks wedwards! (and JoshHoughton)

 

This solved my issue too, at least partially. I was also having the same type of problem when creating a new record on the affected gallery. If I made the new record without filling in the field that the gallery sorts by PowerApps would fill the form with an existing recording after the SaveForm.

 

To get around this I used a context variable I was already using for the SaveForm function to Patch only NewForm situations/modes, and the Last() function in the Item property to force PowerApps to display the latest record, which should always be the newly created one. Described below...

 

My "new record" button is:

NewForm(FormEditCell); Navigate(EphysExpCell, None, { patchLookupEphysCell: true })

And the Item property of the detail form is:

If (patchLookupEphysCell = true, Last('Exp Slice Ephys Cells 2'), First(Filter('Exp Slice Ephys Cells 2',CellSelected = ID)))

And I set the context variable to false when leaving that screen via the Cancel/Back or Delete buttons:

UpdateContext({patchLookupEphysCell: false})

 

An annoyance that still remains is that I can often see PowerApps refreshing the form - showing the wrong or old data first before the above functions get applied. We really shouldn't have to be doing these types of workarounds...

 

Thanks for the special mention everybody 🙂 Does this mean I will be famous now? lol

Thanks so much! You win at life! 🙂

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