Hi community,
I have an App reading from a SharePoint list and a screen with a Refresh button that is not behaving as I expect. When clicked, it should make a loading message start, refresh the data source, collect the data again in local collections, and finally make the loading message disappear.
In the same screen, I am showing values from the local collections, so I can see straight away if an update has worked.
The loading message works fine, but the data does not refresh the first time I click on the button. I need to click twice for the Refresh and the ClearCollect to run completely (as far as I understand?).
I don't understand why and appreciate any help 🙂
I have understood that PowerApps is not always great at understanding sequence of multiple commands. May that be the problem? What is a good work-around then?
I have the following code (EU code, so ; instead of , and so on):
Button.OnSelect=
Set(AppLoaded;false);; <---- the variable AppLoaded makes the loading message visible/invisible
Refresh(ListeAlleUnibuss);;
Concurrent(
ClearCollect(AlnaBusser; Filter(ListeAlleUnibuss; Verksted = "Alnabru"));
ClearCollect(KlemetsrudBusser; Filter(ListeAlleUnibuss; Verksted = "Klemetsrud"));
ClearCollect(RosenholmBusser; Filter(ListeAlleUnibuss; Verksted = "Rosenholm"))
);;
Set(AppLoaded; true)
Solved! Go to Solution.
Coming back after some testing, I have found a solution. Maybe not so elegant, but it does the job!
I found out that the problem was actually not the Refresh, but the ClearCollect. I tested separating the two actions in 2 buttons, but even when ClearCollect was called 5 seconds after the Refresh, it didn't have any effect. It needed to be fired twice to grab the data. So I obliged the App to run ClearCollect twice through a timer.
Every time the user clicks on the Refresh button, the following runs:
Concurrent( Set(AppLoaded; false); <--- I make a loading animation start Refresh(MySharePointList); <--- I call for a refresh of the sharepoint list UpdateContext({CountDown: false});; UpdateContext({CountDown: true}) <---- I make the timer start );; Concurrent( ClearCollect(OneListOfBusses; Filter(MySharePointList; Place = "Lillehammer")); <---- I collect filtered sets of the sharepoint list ClearCollect(AnotherListOfBusses; Filter(MySharePointList; Place = "Tønsberg"))
I then have a hidden timer with Duration 3 seconds, and
Timer.Start = CountDown (the boolean kickstarted in the Refresh button) Timer.OnTimerEnd = Concurrent( ClearCollect(LillehammerBusser; Filter(ListeAlleUnibuss; Verksted = "Lillehammer")); ClearCollect(TonsbergBusser; Filter(ListeAlleUnibuss; Verksted = "Tønsberg")) );; Set(AppLoaded; true)
In other words, I oblige the app to run ClearCollect again after 3 seconds. This did the trick for me. Still, I don't know why ClearCollect doesn't run the first time xD
Case solved, but if you have any ideas on how to do it better, I'd be glad to hear! 🙂
Hi @Ginevra ,
Here's a similar problem that someone met for your reference:
I suggest you split up the formulas. For example, you could set the Refresh funtion to the Screen's OnVisible.
Best regards,
Community Support Team _ Phoebe Liu
Hi @v-yutliu-msft ,
Unfortunately the other user case you refer to did not help.
Splitting the formula so one part is in the OnVisible screen property does not solve my case: the user may have this screen open all the time, and want to receive updates if, e.g. the SharePoint list is updated from SharePoint.
In my case, I need PowerApps to first refresh the datasource, then collect it in local collections. Data from these are shown in the screen. I put the two formulas one after the other, separated by ; .
But it seems to me like PowerApps sometimes jumps over my Refresh command, or does it after the ClearCollect.
Does anyone have a technical understanding of how PowerApps computes sequential commands, and how you can better control it?
Coming back after some testing, I have found a solution. Maybe not so elegant, but it does the job!
I found out that the problem was actually not the Refresh, but the ClearCollect. I tested separating the two actions in 2 buttons, but even when ClearCollect was called 5 seconds after the Refresh, it didn't have any effect. It needed to be fired twice to grab the data. So I obliged the App to run ClearCollect twice through a timer.
Every time the user clicks on the Refresh button, the following runs:
Concurrent( Set(AppLoaded; false); <--- I make a loading animation start Refresh(MySharePointList); <--- I call for a refresh of the sharepoint list UpdateContext({CountDown: false});; UpdateContext({CountDown: true}) <---- I make the timer start );; Concurrent( ClearCollect(OneListOfBusses; Filter(MySharePointList; Place = "Lillehammer")); <---- I collect filtered sets of the sharepoint list ClearCollect(AnotherListOfBusses; Filter(MySharePointList; Place = "Tønsberg"))
I then have a hidden timer with Duration 3 seconds, and
Timer.Start = CountDown (the boolean kickstarted in the Refresh button) Timer.OnTimerEnd = Concurrent( ClearCollect(LillehammerBusser; Filter(ListeAlleUnibuss; Verksted = "Lillehammer")); ClearCollect(TonsbergBusser; Filter(ListeAlleUnibuss; Verksted = "Tønsberg")) );; Set(AppLoaded; true)
In other words, I oblige the app to run ClearCollect again after 3 seconds. This did the trick for me. Still, I don't know why ClearCollect doesn't run the first time xD
Case solved, but if you have any ideas on how to do it better, I'd be glad to hear! 🙂
Hi
This was also driving me crazy, your post showed me that I wasn't alone!
After the second refresh the data comes back OK
I'm looking at a SQL data source, and I have a filter on it, when the filter is taken off it works fine, so no need to double refresh. Also issue happens if I try to sort the data
Both Filter and Sort delegate OK to the SQL DB, but suspect issue is because delegation in conjunction with Collections and filters has an issue, I suspect if you take the filters out of your ClearCollect commands it will not need the double refresh (Make sure to take the filtesr out of all ClearCollect commands that are in the same statement)
While this solves my problem, it's not ideal, as I need to apply the filter, so I have to now refresh twice in an APP designed for offline capability, so it slows it down
My workaround maybe to make some views in SQL.... that I can connect to without the use of filters
Let me know if that helps!
Hei @bkeano , thanks for your reply. I didn't think about that Filter could be the issue, that's noted down!
Long time stale this post, but I found it so maybe someone else might find this useful.
Turning off the experimental feature: "Use longer data cache timeout and background refresh" fixed this for me.
In fact, using the timer to re-cache the data did not work for me when this feature was turned on.
When I turned it off, it started working - on the first refresh and clearcollect - without having to use the timer.
Thanks for taking the time to update this post. You really helped me out. Turns out that experimental feature is present in older ( pre mid 2020??) versions. Today if you turn it off, it disappears from Advanced Experimental Features. Its default status in the older apps is apparently Enabled as it is Enabled in our other apps.
I had a formula on a Button that did a Patch to a large SharePoint list and did an UpdateIf and a RemoveIf to a smaller list. On the first click the UpdateIf and RemoveIf would execute, but not the Patch. If you clicked the Button a second time the Patch executed. Chased my tail for a long time on this. When I turned off the Experimental Feature you named, the Formula worked as intended. Thanks Again.
This may be a relatively old thread, but it seems issue still persists.
I have a forall/patch to run after a removeif to renumber a list of scenarios. If they exist as is, the forall/patch does not fire. What's strange is I've experimented with a notify() command in various places before and after the forall/patch and it always works. Yet the forall/patch only seems to work if i comment out (//) the removeif statement!
In my powerapps version (3.21081.49), there is no feature to toggle as described above. Looks like i'm going to have to resort to the ugly and inelegant timer method as described!
I've noticed this "bug" elsewhere in powerapps where variable settings/functions appear to get skipped or happen in the wrong order. It's not always easy to repeat. It would be handy to have an opposite to the concurrent() function to ensure a serialisation of function calling and ensuring the next step only occurs on completion of prior. Been tearing my hair out on this one!!!
I also meant to say i had a refresh() after the removeif....
Anyway, just moved the forall/patch to timer with 1s delay and its working. Very inelegant! I wish there was a way to monitor the sequence of execution and to enforce a command to finish before carrying on the sequence....
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