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

Button goes back to default color after refresh

Button 1 is pressed so it changes the color from blue to yellow and it should stay yellow even if the browser get refreshed. 

But right now if the browser get refreshed the app starts from scratch.!!

 

Any idea's?

2 ACCEPTED SOLUTIONS

Accepted Solutions
RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

We are all learning every day 🙂

Just a caution - this might be a bit tedious depending on how many buttons you want to do this for.  If you can't avoid people refreshing the entire browser then keep reading...

 

You can create a list in your site and call it ButtonStatesList or something.  

Add columns to identify the button and its state - you can use the default Title column for the button and add a single-line-of-text column called "State". 

Back in your PowerApp, add a datasource by clicking on the data icon on the left of the screen and Add Data - find Sharepoint and add a Sharepoint data source.  Then on the right find and select your site and select your ButtonStatesList.  

With your list connected to your app, add a button and change it's name to "Button1" - you can do this by selecting the button and then either on the right where you see it's name above the properties you can edit the name, or if you're using the Tree View on the left just double-click the button in the tree view and you can rename it.  You can call it whatever you want, it won't change anything other than your ability to easily identify it while looking at your app - what's important is what the buttons saves to SharePoint in the Title column that will associate it with it's own state.

Set the OnSelect: property of your button to;

 

 

With({buttonRecord: LookUp(ButtonStatesList, Title="Button1")}, 
//gets the existing button record, if it exists and places it into a variable called "buttonrecord" that we can reuse later in our formula

If(IsBlank(buttonRecord.State), 
//checks if there's an existing record by checking if the state is blank - i.e. nothing has been captured yet

  Patch(ButtonStatesList, Defaults(ButtonStatesList), {Title: "Button1", State: "On"}), 
  //if it is blank, then we assume there's no record yet and create one the first time the button is pressed, and set it's state to "On"

  Patch(ButtonStatesList, buttonRecord, {Title: "Button1", State: If(buttonRecord.State="Off", "On", "Off")}) 
//if it's not blank, then the record already exists so we update the existing record, setting it to "On" if it's currently "Off" and "Off" if it's currently "On"

)

)

 

 

 Now go to your button Fill: property and set it as follows;

 

 

If(LookUp(ButtonStatesList, Title="Button1", State)="On", Yellow, Blue)

 

 

That should do it.  If you add more buttons, just make sure each button is set to check for whatever Title it's capturing when pressed - Just replace the above with "Button2", "Button3" etc. as you go.  Whenever your app is loaded, the button will get it's Fill color from the list.

You should note this will work fine for one person using the app - PowerApps will refresh the state automatically whenever it's updated by that user for that PowerApps session - but nobody else will see the update unless their app is continuously checking for it, or they update the color themselves and force a refresh for their session.  If you want everyone to see state updates whenever someone else updates them, you'll have to add a timer to Refresh() the data source periodically.  To do this, just add a time control and set the following properties;

  • Duration: 15000 (refreshes every 15 seconds)
  • Repeat: On/true
  • AutoStart: On/true
  • OnTimerEnd: Refresh(ButtonStatesList)
  • Visible: false
  • AutoPause: On/true if your buttons only exist on one screen, Off/false if they are spread across multiple screens

You Hope this helps 🙂

RT

View solution in original post

RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

I have some questions - because I don't see how your formula is figuring out which button information it's fetching - and based on your example you need to track the status for three buttons independently.  Is this still what you're trying to do, or did I miss something?

If this is what you're trying to do, then you need to save each button's data and be able to retrieve it, so your buttonState list should have;

  • Three rows with two or three columns - one column for each button that identifies each button uniquely, (initially we were using the Title column) plus at least one column to track clickCount, or two if you're still tracking the button clicked status
Title (Text)clickCount (Number)
Button1 
Button2 
Button3 

Each button should patch it's own Title for future lookups, incrementing it's clickCount.

What I'm seeing in your code is different behaviour;

  • Your lookup is fetching a row from a list called SafetyCross, where the Title is = gblClickCount.  
  • Your Patch statement is likewise patching gblClickCount into the title. 

How is this different for each button?

How are you identifying individual buttons in your Patch or LookUp statements?  

What does this list currently look like?

 

Also, with your Patch, you're saving two identical values - buttonClicks and clickCount.  Are these not the same thing?

 

Admittedly, there are always many ways to achieve the same thing, and you should do what makes you comfortable - but also what makes sense to you.  I built an example using a collection instead of SharePoint, but this should show what I see as your ask - if it's different to this then I'm on the wrong track.

If it's accurate, feel free to download the msapp file attached to see how it was done - you can open it using "Open", "Browse Files" from the maker portal and select the file you downloaded.  Here's what it looks like;

 

buttonClick.gif

 

 

Kind regards,

RT

View solution in original post

17 REPLIES 17
RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

The entire app will restart if the browser is refreshed, and all components will be reset to their default state, so this is unavoidable unless you save the state of the button outside the app - for example in a sharepoint list somewhere - and then load the state when the app starts.

Kind regards,

RT

Anonymous
Not applicable

Hello @RusselThomas 

Thanks for the respons dear.

let me just say that i am very new to powerapps. 

I have a sharepoint list and its connected to the app, i just dont know how to record the button status to a column. 

RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

We are all learning every day 🙂

Just a caution - this might be a bit tedious depending on how many buttons you want to do this for.  If you can't avoid people refreshing the entire browser then keep reading...

 

You can create a list in your site and call it ButtonStatesList or something.  

Add columns to identify the button and its state - you can use the default Title column for the button and add a single-line-of-text column called "State". 

Back in your PowerApp, add a datasource by clicking on the data icon on the left of the screen and Add Data - find Sharepoint and add a Sharepoint data source.  Then on the right find and select your site and select your ButtonStatesList.  

With your list connected to your app, add a button and change it's name to "Button1" - you can do this by selecting the button and then either on the right where you see it's name above the properties you can edit the name, or if you're using the Tree View on the left just double-click the button in the tree view and you can rename it.  You can call it whatever you want, it won't change anything other than your ability to easily identify it while looking at your app - what's important is what the buttons saves to SharePoint in the Title column that will associate it with it's own state.

Set the OnSelect: property of your button to;

 

 

With({buttonRecord: LookUp(ButtonStatesList, Title="Button1")}, 
//gets the existing button record, if it exists and places it into a variable called "buttonrecord" that we can reuse later in our formula

If(IsBlank(buttonRecord.State), 
//checks if there's an existing record by checking if the state is blank - i.e. nothing has been captured yet

  Patch(ButtonStatesList, Defaults(ButtonStatesList), {Title: "Button1", State: "On"}), 
  //if it is blank, then we assume there's no record yet and create one the first time the button is pressed, and set it's state to "On"

  Patch(ButtonStatesList, buttonRecord, {Title: "Button1", State: If(buttonRecord.State="Off", "On", "Off")}) 
//if it's not blank, then the record already exists so we update the existing record, setting it to "On" if it's currently "Off" and "Off" if it's currently "On"

)

)

 

 

 Now go to your button Fill: property and set it as follows;

 

 

If(LookUp(ButtonStatesList, Title="Button1", State)="On", Yellow, Blue)

 

 

That should do it.  If you add more buttons, just make sure each button is set to check for whatever Title it's capturing when pressed - Just replace the above with "Button2", "Button3" etc. as you go.  Whenever your app is loaded, the button will get it's Fill color from the list.

You should note this will work fine for one person using the app - PowerApps will refresh the state automatically whenever it's updated by that user for that PowerApps session - but nobody else will see the update unless their app is continuously checking for it, or they update the color themselves and force a refresh for their session.  If you want everyone to see state updates whenever someone else updates them, you'll have to add a timer to Refresh() the data source periodically.  To do this, just add a time control and set the following properties;

  • Duration: 15000 (refreshes every 15 seconds)
  • Repeat: On/true
  • AutoStart: On/true
  • OnTimerEnd: Refresh(ButtonStatesList)
  • Visible: false
  • AutoPause: On/true if your buttons only exist on one screen, Off/false if they are spread across multiple screens

You Hope this helps 🙂

RT

Anonymous
Not applicable

@RusselThomas 

 

You did it, thank you dear 👍

Anonymous
Not applicable

 

Hello @RusselThomas 

Could you help me again please? 

I have these 3 buttons that changes 7 different colors one color pr. click. i want to patch button values to my sharepoint list so when i restart the app the buttons stays at same color and dont go back to default. Just the same like the first problem but now the buttons changes between 7 colors. 

 

 

 

 

 

 

The code is for each button: 

On.Select

If(gblClickCount<7;Set(gblClickCount;gblClickCount+1);Set(gblClickCount;1));;

 

 

 Fill.
Switch(gblClickCount;
 
1; Green;
 
2; Yellow;
 
3; SkyBlue; 
 
4; Orange;
 
5; MediumPurple;
 
6; Red;
 
Capture1.PNG
RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

So at this point, the user experience becomes a critical deciding factor in how you take it forward.

Do you want each user to keep track of their own button clicks, or are the button states universal (the same) for all users?  i.e. if I click button 3 through to Orange and you're running the app, do you want to see button 3 change to Orange?  Or do you want to track your own button clicks independent from mine?

Kind regards,

RT

Anonymous
Not applicable

@RusselThomas 

Thank you for your respons.

All users should be the same there is only one display for this app. I just dont want to lose any data when the app gets refreshed in the web browser . 

 

Best regards 

 

 

RusselThomas
Community Champion
Community Champion

Hi @Anonymous ,

That makes it easier, as you're already saving a row of data for each button 'state'.

All you need to do is add a number column to your button state list - call it 'buttonClicks' or something that makes sense to you - this is where you can store the number of clicks the button is on.  Remember to refresh the data source in PowerApps after you've added the column to SharePoint ("Data" menu, "..." next to your data source, "Refresh")

If we take a step back and look at the solution, it may make more sense to keep your number/colour reference as a lookup table than just existing in logic.  By this I mean, instead of switching the value of ClickCount for each button to get the fill colour, it would be better to store the clickcount/fillcolour in a table and just look it up.

This way, if you want to change the colour of a number, you don't have to go and edit three buttons worth of code to do it.

There is a behaviour called App Start you can use to initialise information for your app.  This will run exactly once, when your app starts.  You can put any behaviour functions in app start, including collecting data from a source, setting variables, or in this case, creating a reference table for your app to use.

On your left navigation menu, above your first screen (usually Screen1), you should see "App". Click on this, and then make sure your formula bar property is set to OnStart (the down arrow to the left of the fx on the formula bar).

This can go in your OnStart: property;

 

ClearCollect(collectClickColours; {
  numClicks: 1; fillColour: Green;
  numClicks: 2; fillColour: Yellow;
  numClicks: 3; fillColour: SkyBlue;
  .....
  });;

 

So here we'll set up our collection called collectClickColours with a column "numClicks" and corresponding "fillColour" (you can call the columns what you like, as long as it makes sense to you - just replace the ..... with the rest of the numbers and colours - I'm lazy 🙂)

Our buttons will reference this table to get their colours - and if we want to change a numbers colour, we only have to do it here, once.

 

Now your buttons' Fill: properties can look as follows;

 

LookUp(collectClickColours;
     numClicks = LookUp('buttonStatesList'; Title='Button1'; clickCount); fillColour
)

 

 If there's only one screen/user, you don't have to worry about refreshing - and if the app 'reboots', then it should fetch the last saved click counts.

[Edit]

I forgot to add, you'll want to include the clickcount incrementer in your button OnSelect: patch update.  Editing the code from the original post, it would look something like this;

With({buttonRecord: LookUp(ButtonStatesList, Title="Button1")}, 

If(IsBlank(buttonRecord.State), 

  Patch(ButtonStatesList, Defaults(ButtonStatesList), {Title: "Button1", State: "On", buttonClicks: 1}), 
  
  Patch(ButtonStatesList, buttonRecord, {Title: "Button1", State: If(buttonRecord.State="Off", "On", "Off"), buttonClicks: buttonRecord.buttonClicks+ 1})
)

)

Try it out and let me know how it goes 🙂

Kind regards,

RT

Anonymous
Not applicable

Hello @RusselThomas

Its recording to the sharepoint list but i getting error when i am adding the code OnStart: 2.PNG 

 

Helpful resources

Announcements

Copilot Cookbook Challenge | Week 3 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  n/a2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a     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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Parul_Yadav_Neo1. n/a2. SpongYe2. n/a3. n/a3. n/a4. n/a4. n/a5. n/a5. n/a

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

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by the end of July with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Top Solution Authors
Top Kudoed Authors
Users online (2,920)