cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Phineas
Community Champion
Community Champion

Retain Exit Settings for Next OnStart

I have a main screen that has a series of buttons that allow for users to navigate through the app.

 

I have a toggle (Toggle1). I use the toggle to shutdown access to the site through the buttons referenced above.

 

The default setting of Toggle1 is 'true'. If for some reason the owner wants to limit access to the site for a period of time the owner can set Toggle1 to 'true' and all of the site buttons will default to 'Disabled'.

 

My issue, if the owner sets Toggle1 to off and then exits the site, when the owner returns the Toggle has reset to 'false' and all the button are back to 'Edit'.

 

How do I set it up so that the setting of Toggle1 is how the site open during the next viewing?

17 REPLIES 17

I didn't mean to confuse things.

 

I have visual concept clarity issues.

 

It takes my time to see some things.

 

The table I referenced was created in a flow, for another pupose - you are correct I apologize.

     

Set(varVisible, LookUp(UserSettings, AppUserName = User().Email).varVisible);
Set(dispToggle, LookUp(UserSettings, AppUserName = User().Email).dispToggle);
Set(defaultLocation, LookUp(UserSettings, AppUserName = User().Email).defaultLocation);

 

Merely placing the above n the OnStart is going to force Toggle1 to default to the closed position when the app was last saved, yes? There is nothing else I need to do?

 

I've made a few edits to match my fields. Should the below deliver the outcome I desire?

Set(varVisible, LookUp(UserSettings, AppUserName = User().FullName).varVisible);

Set(Toggle1, LookUp(UserSettings, AppUserName = User().FullName).Toggle1);

Set(defaultLocation, LookUp(UserSettings, AppUserName = User().FullName).defaultLocation)


@Phineas wrote:

     

Set(varVisible, LookUp(UserSettings, AppUserName = User().Email).varVisible);
Set(dispToggle, LookUp(UserSettings, AppUserName = User().Email).dispToggle);
Set(defaultLocation, LookUp(UserSettings, AppUserName = User().Email).defaultLocation);

 

Merely placing the above n the OnStart is going to force Toggle1 to default to the closed position when the app was last saved, yes? There is nothing else I need to do?

 

I've made a few edits to match my fields. Should the below deliver the outcome I desire?

Set(varVisible, LookUp(UserSettings, AppUserName = User().FullName).varVisible);

Set(Toggle1, LookUp(UserSettings, AppUserName = User().FullName).Toggle1);

Set(defaultLocation, LookUp(UserSettings, AppUserName = User().FullName).defaultLocation)


The code I posted above will read three values from a list called UserSettings (that already exists and has data in it) and put those into three variables I use in that particular app. Copying the code and changing the names to match some of your control names is only part of making it work. Do you also have a list called UserSettings connected to your app and does it have the exact same columns as my list? If not, you'll need to adjust this code further.

 

The other part is, and you recognized this in an earlier post, any changed variable data needs to get saved back to the list if you want to use it in the future. You correctly recognized that the Patch() function works for this. If there is no data for the LookUp() function to read in the first place, the app won't set proper values to the variables.

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.

Ok, I've changed the condition to include only fields/columns in my lists.

 

Set(varVisible, LookUp(ComplianceList, FullName = User().FullName).varVisible); 

     - This looks for the default setting on the list, yes?

 

Set(Toggle1, LookUp(ComplianceList, FullName = User().FullName).Toggle1);

     - This sets the default setting of Toggle1 based on the content of the field at OnStart, yes?

 

Set(defaultLocation, LookUp(ComplianceList, FullName = User().FullName).defaultLocation)

     - What does this do?

 

Consequently, how should the Patch look, where should I place the Patch command for Toggle1 (I know there is a difference between OnCheck, OnUncheck, OnChange)  go, and where is the Patch sending the information?

 

I don't have a Patch and I don't have a list or table that is currently collecting the default status of Toggle1.

 

Patch(...


@Phineas wrote:

Ok, I've changed the condition to include only fields/columns in my lists.

 

Set(varVisible, LookUp(ComplianceList, FullName = User().FullName).varVisible); 

     - This looks for the default setting on the list, yes?

 

Set(Toggle1, LookUp(ComplianceList, FullName = User().FullName).Toggle1);

     - This sets the default setting of Toggle1 based on the content of the field at OnStart, yes?

 

Set(defaultLocation, LookUp(ComplianceList, FullName = User().FullName).defaultLocation)

     - What does this do?

 

Consequently, how should the Patch look, where should I place the Patch command for Toggle1 (I know there is a difference between OnCheck, OnUncheck, OnChange)  go, and where is the Patch sending the information?

 

I don't have a Patch and I don't have a list or table that is currently collecting the default status of Toggle1.

 

Patch(...


I'll describe what Set(varVisible, LookUp(ComplianceList, FullName = User().FullName).varVisible) does to help you understand what's going on here: This lookup searches for the first record in ComplianceList that the current user's name matches a value in the FullName column. When this lookup finds that first match, it will return the value stored in the varVisible field of that same record. Set() will point the global variable varVisible to this return value from the lookup.

Your app may not need all of these lookups - they are simply ones I used in one of my apps. dispToggle and defaultLocation are additional columns & variables I used in my app and your app may not require these.

To Patch() a value back to the list (in a behavior formula, usually right after the variable was changed by Set), use code like this:

Patch(ComplianceList,
    LookUp(ComplianceList, FullName = User().FullName),
    {
    varVisible: varVisible
    }
)

 

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.

Okay, its starting make a little sense. 😂

 

So, I need to create a List that has a column that stores the default/Patch setting of Toggle1, yes?

 

I should place the Patch command in the 'OnChange' property of Toggle1, yes?

 

I should place a condition in the 'OnStart' of the app, yes? The list I will create for this won't have anyone name in it to match. Whatelse should/can I use in the condition. The list will have one row with one column 'ToggleStatus', set to default in SharePoint to 'true', with the Patch changing it back and forth between 'true/false'.

     Set(Toggle1, LookUp(ComplianceList, FullName = User().FullName).Toggle1);

 


@Phineas wrote:

 

So, I need to create a List that has a column that stores the default/Patch setting of Toggle1, yes?

 

Yes, that's correct.

 


@Phineas wrote:

 

I should place the Patch command in the 'OnChange' property of Toggle1, yes?

 

Yes, that would be a good place to put it.

 


@Phineas wrote:

 

I should place a condition in the 'OnStart' of the app, yes? The list I will create for this won't have anyone name in it to match. Whatelse should/can I use in the condition. The list will have one row with one column 'ToggleStatus', set to default in SharePoint to 'true', with the Patch changing it back and forth between 'true/false'.

     Set(Toggle1, LookUp(ComplianceList, FullName = User().FullName).Toggle1);

 


You have a couple of choices here:

  1. You can pre-populate your list with values, or
  2. You can modify your OnStart code to check to see if a LookUp for that user returns a valid value, and if not you set the variable to a preselected default value

 

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.

Right now the Toggle1 default property is 'true'.

 

How do I write the Lookup in the 'OnStart' to make it pull in the current content of the column in the List? The only column in the List is 'SiteStatus', with the content of 'true' (by default).

 

     Set(Toggle1Default, Lookup('Site Start Up List',...)

I'm not quite sure I understand where you are going with this question: You should ensure all necessary columns are present in your list and make sure there are values present (or your app knows how to handle the case with no values). A LookUp will return blank if it finds no matching record.

 

If you want to pull any value from this list, one way is with First():

First('Site Startup List').SiteStatus

This pulls up the value in the SiteStatus column from the first record in the list.

 

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a 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