cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

refresh() against sharepoint doesn't update

Hi folks.  I have a powerapp with a O365 sharepoint list backend (maybe 2k records).  I am having trouble keeping it synced and accurate from sharepoint; it also has intermittent ETAG issues. 

In the onvisible of my main screen I populate a variable: 

 

Refresh('Sharepoint list');
UpdateContext({Current_Comments: Comments_DataCard1.Default});

 

Then in that screen, there is an html input control and an "add comment" button with the follow onselect code:

 

If(IsBlank(Comment_Input),Notify("No comment to post",Error),
    Refresh('Sharepoint list');
    UpdateContext({Current_Comments: Concatenate(Office365Users.MyProfile().DisplayName, " ", Text(Now(),ShortDateTime), ": ", Comment_Input.HtmlText, Current_Comments)});
Patch('Sharepoint list', ThisItem, {Comments: Current_Comments});
Reset(Comment_Input); Refresh('Sharepoint list'))

 

I also have a text box with 

 

HtmlText = Current_Comments

 

to show the full history of comments.  

Behavior: If you add a comment with the button, it will instantly update in the text box.  However, if you go to another screen and come back, the text box will revert to the previous comment value.  This confuses me: the onvisible of the main screen should re-pull the most recent, post-patched comment value and push it into the variable, which then should display.  

Waiting does not help - unless you reload the entire app, the new comment will not show up.  I can confirm that the patch successfully committed by checking the sharepoint list - the new comment value is there sometime between 30 seconds and 5 minutes.  

Using the powerapps monitor indicates that a refresh is running much less frequently than I've coded.  Maybe powerapps is cleverly choosing to ignore refreshes in an attempt to make it more performant?

I've also added error handling per this solution around the patch code because my users have reported "lost comments" .  No errors have been seen.  

How can I instruct my powerapp to actually pull the most recent comments value from the sharepoint list?  I think this may also be causing race conditions with a silent discard of the older commit, as concurrent users may be trying to comment back and forth to each other.

12 REPLIES 12
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @DylanEvans ,

Breaking this down a bit, this code

If(
   IsBlank(Comment_Input),
   Notify("No comment to post",Error),
   Refresh('Evidence Request');
   UpdateContext(
      {
         Current_Comments: 
         Concatenate(
            Office365Users.MyProfile().DisplayName, 
            " ", 
            Text(Now(),ShortDateTime),
            ": ", 
            Comment_Input.HtmlText, 
            Current_Comments
         )
     }
   );
   Patch(
      'Evidence Request', 
      ThisItem, 
      {Comments: Current_Comments}
   );
   Reset(Comment_Input); 
   Refresh('Evidence Request')
)

Sets a Context Variable Current_Comments by combining a heap of information and the updates a field in the current record in the SharePoint list 'Evidence Request'  (I assume this code is run from within a form or gallery as it refers to ThisItem) with this Variable value. It then refreshes the SharePoint list - all looks good.
Now this bit

Refresh('Sharepoint list');
UpdateContext({Current_Comments: Comments_DataCard1.Default});

Firstly, is this 'Evidence Request' you are refreshing?
The second bit however may be your issue if you simply want to see your current comments - two things here
Are you on a different screen? If so Current_Comments as a Context Variable is actually a different Variable, but more the issue is this bit Comments_DataCard1.Default. Try Comments_DataCard1.Text, however I would suggest a much simpler approach - set a Global Variable

If(
   IsBlank(Comment_Input),
   Notify("No comment to post",Error),
   Refresh('Evidence Request');
   Set(
      Current_Comments,
      Concatenate(
         Office365Users.MyProfile().DisplayName, 
         " ", 
         Text(Now(),ShortDateTime),
         ": ", 
         Comment_Input.HtmlText, 
         Current_Comments
       )
     )
   );
   Patch(
      'Evidence Request', 
      ThisItem, 
      {Comments: Current_Comments}
   );
   Reset(Comment_Input); 
   Refresh('Evidence Request')
)

then don't bother resetting it on the OnVisible - it will be available across all screens. If you don't need to see it, or need ti reset, just use

Set(Current_Comments,Blank())

at the appropriate place.

 

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.

Good questions.  All this is happening on the same main screen.  And yes, that is the same sharepoint list - I had incompletely sanitized my references when pasting in the code, and have now edited the original post so that they all match.  

The reason I'm doing this rigmarole with a patch() and context variable is because I don't want the user to set the new text that will be saved to the sharepoint.  The app should take some of their input, add context, then push it into the sharepoint list as an append of what's already there.  Per all the doc I've read, I can't seem to do that with a submitform because you can't set the value of a card through code.

 

The global variable may cause issues because this main screen is basically an item detail screen, and its value depends on the ThisItem selected.  I would need to reset it to the new ThisItem.Comment.Value every time a new item was selected from the gallery screen.  If my OnVisible refresh isn't getting processed, I'd expect to have the same problems in updating the universal comment variable.  

 

I mostly don't see why refresh isn't occurring when I ask it to happen - neither in the "Add Comment" button code or in the Onvisible code.  How do I ask Powerapps to go re-pull a sharepoint value on-demand?  

Thanks @DylanEvans ,

I am not sure I have my mind completely around your logic, however the key points

Patch(
   'Evidence Request', 
   ThisItem, 
   {Comments: Current_Comments}
);
Reset(Comment_Input); 
Refresh('Evidence Request')

writes your comments to the list and then refreshes it - now

UpdateContext({Current_Comments: Comments_DataCard1.Default});

Updates the Variable - with the current value from the list

One issue I mentioned before - why the Default reference? What does CommentsDataCard1.Text get for you?

 

 

 

Good summary of the logic.  

Using CommentValue.Text instead of CommentDatacard.Default yields no change: I replaced every reference, but still have the same issue: after pushing my button (logic: refresh(), updatecontext(), patch(), refresh()), the variable updates correctly, but the CommentValue.Text does not change.  

Likewise, going into another screen and coming back reverts the variable back to the value of CommentValue.Text. 

In neither the Onvisible nor button code are the refreshes working: the CommentValue.Text is not getting updated to the value in the sharepoint list.  It can't be explained by timing, either: it takes about 26 +/- 9 seconds for the new value to show up in the sharepoint list, and going out and back in 10 minutes later will not pull the new comment value.  

@DylanEvans ,

Very strange what about this
First bit OK

Patch(
   'Evidence Request', 
   ThisItem, 
   {Comments: Current_Comments}
);
Reset(Comment_Input); 
Refresh('Evidence Request')

now this OnVisible

UpdateContext(
   {
      Current_Comments: 
      Lookup(
         'Evidence Request'
         ID=YourGalleryName.Selected.ID,
         Comments
      )
   }
)

You should not have to do this, but it should work.

 

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.

Hi Warren - I figured it out.  Well, the problem anyway - not the solution yet.  The problem was that everything in this screen was based on a collection, so was cached.  In the earlier screen (call it ChooseItem), I populate a collection using a filter against the backend sharepoint list.  This main screen is like an Item detail screen that shows different parts of the record and lets actions be taken on it, including commenting on it.  

I just realized/re-read that collections are a local cache of a datasource, so every time I was calling refresh(), it was against the datasource, and the collection was happily unaffected.  I had assumed that a refresh against a datasources would update associated collections as in the style of a database view or a powerbi reference.  No.  
So what I need to do is trigger an update on the collection record after (or maybe also before) each patch().  I tried the following in place of the refresh()s, 

Update(MyCollection,ThisItem,LookUp('Datasource', ID=ThisItem.ID));

but it still doesn't change the CommentValue.Text field in the screen.  I feel like I'm close, though: The second part (clearly based on your last recommendation) does work as a standalone: if I have a text box with 

HTMLText=NewTempComment.Comments

and a "Comment Refresh" button that executes: 

UpdateContext({NewTempComment: LookUp('DataSource', ID=ThisItem.ID)})

pushing the "Comment Refresh" button after adding a comment will make the new text box show the latest comment.  
Why won't the Update() refresh the current record in my collection as promised?

Aright, now I'm really confused: how exactly does Powerapps handle data between collections and datasources?  The form autogenerated in my Item Detail Screen by Powerapps has 

DataSource = [@my_data_source]

 Not 

Datasource = [@My_Collection]

even though I built it off the collection-based gallery.  Is my ItemDetail form referencing the collection or the datasource?  

 

Hi @DylanEvans ,

A heap of questions and you have made some correct assumptions, but headed slightly off course on others.

A collection as you correctly stated is a temporary table "cached" (your word) in the app. It is independent of the table and needs to be refreshed either by re-collecting (all the data) or updated with the same information when at the same time as the table. A lot of users update the collection and then when happy all is done, write this to the table. However to your Update - syntax below

UpdateIf(
   MyCollection,
   ThisItem,
   {
      CollectionField1:ValueToUpdate1,
      CollectionField2:ValueToUpdate2
   }
)

Your last question - you have to change the DataSource if you want it to use your collection. Power Apps has no idea what you want to use it for - that is why they are called Canvas Apps.

 

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.

 

Hi @DylanEvans ,

Just checking if you got the result you were looking for on this thread. Happy to help further if not.

 

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.

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,889)