Hello,
I have a multi-tab form app I am working on. The Requestor and those working the request (admins) can edit the Request and Comments tabs, but only the admins can edit the Designer and Model Shop tabs.
Request Tab
What I have achieved so far: The form defaults to view mode. If any of the users (requestors or admins) have click on the Request tab, the Edit icon is displayed. When they click the Edit icon, the fields open up and Save and Cancel icons are displayed. All OnSelect form actions work (please see attached formulas). The part I am struggling with is visibility. The icons are always visible no matter which tab is clicked. I need them to disappear when the Model Shop or Designer tab is clicked.
Designer Tab and Model Shop Tab
While all users are allowed to see the information on these forms, only admins are allowed to edit the information. I would like to create two separate sets of icons for these 2 tabs that are only visible if the logged in person is an admin. I realize that in theory, I could have one big form and set the visibility of the data cards to show depending on which tab is clicked, but with 18 fields on one form and 9 on the other, I decided to hold off unless you tell me it is absolutely necessary. It's okay if it is, I just didn't want to go through all the extra work if it wasn't. I followed Reza's @Reza instructions ("Check if User is a Member of SharePoint Group in Power Apps") on how to set up a variable called isAdmin that checks to see if they are part of a SharePoint Security Group. Thanks for that video Reza. I just need to know how to apply it to this kind of complicated situation.
Comments Tab
The Comments tab has its own controls so we don't have to worry about that one.
You can view all of my app variables and screenshots in the second document called "App Variables". I would rather err on the side of providing too much info than not enough.
Thank you in advance for your help,
Teresa
Solved! Go to Solution.
Hello Sik,
Thank you so much for your guidance! I wouldn't have been able to figure this out without your help. Here are the formulas that ended up working for me in the sense that each set of edit/save/cancel icons is only visible when its tab is clicked, that the Edit and Save/Cancel icons toggle correctly depending on which mode I am invoking and finally that the edit/save/cancel icons are only visible to app admins when the Designer and Model Shop tabs are clicked.
Request Tab:
OnSelect: Set(varFormTab, "Request")
Request Tab Edit Icon:
OnSelect: EditForm(frmRequestVE);UpdateContext({ReqEditlbl:true})
Visible: varFormTab="Request" && If(ReqEditlbl=true,false,true)
Request Tab Save Icon:
OnSelect: UpdateContext({ReqEditlbl:false});SubmitForm(frmRequestVE);ViewForm(frmRequestVE)
Visible: varFormTab="Request" && If(ReqEditlbl=true,true,false)
Request Tab Cancel Icon:
OnSelect: UpdateContext({ReqEditlbl:false});ResetForm(frmRequestVE);ViewForm(frmRequestVE)
Visible: varFormTab="Request" && If(ReqEditlbl=true,true,false)
Designer Tab:
OnSelect: Set(varFormTab, "Designer")
Designer Edit Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,false,true)
Designer Save Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,true,false)
Designer Cancel Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,true,false)
Req Edit Label (only 1 label is needed for all the sets - I toggle the Visible property to off/false once I am done testing):
Text: If(ReqEditlbl=true,"Save","Edit")
The Model Shop formulas are the same as the Designer formulas with the exception of the tab name. I am attaching a document that includes other fine tuning details in case anyone who happens upon this post is interested in taking a look.
Again, thanks so much. I really appreciate your taking the time to help me.
Kind regards,
Teresa
Hi @tagustin2020 ,
Request Tab:
I just feel confused with ReqEditlbl which is more like a update context variable? Another question is that are the four Tabs in a gallery?
The issue of Edit/Save/Cannel icon is because the logic in Visible property is not clear enough. You need to add explicit logic to determine which tab is selected, for example:
TabGallery.Selected.Value="Request" && ReqEditlbl= false //EditIcon.Visible property
TabGallery.Selected.Value="Request" && ReqEditlbl= true //SaveIcon.Visible property
TabGallery.Selected.Value="Request" && ReqEditlbl= true //CannelIcon.Visible property
Designer Tab and Model Shop Tab:
You can create two separate forms for each tab and control the form visible, or create a big form with all data cards for all Tabs and control the visible of card. Both solution are feasible, and the latter may be slightly superior in performance.
As for how to implement this Admin logic, you can determine whether the login user is Admin by getting a member of the Sharepoint Admin Group as you mentioned, or more simply by going through Office365 Group.
Add all administrators to an Office365 group( named AdminGroup), and then in App.OnStart to check if login user is Administrator.
If("AdminGroup" in Office365Groups.ListOwnedGroupsV3().value.displayName, Set(IsAdmin,true),Set(IsAdmin,false))
Then configure the Visible of Form or data cards based on IsAdmin variable.
It may not be perfect for your situation, but hopefully the above will give you inspiration.
Hope this helps.
Sik
Thank you for the advice Sik. I managed to break my app yesterday while attempting to introduce sorting functionality to my Gallery. I'll try these variable adjustments once I have visibility to the forms again. I promise to circle back around as soon as I can. Have a nice afternoon. Teresa
Hello Sik,
My forms are back up and running so I went in to give this a try, but unfortunately is not working. The names of my button tabs are tabRequest, tabDesign and tabModelShop if that helps. The screen does not contain a gallery only Edit forms and buttons made to look like tabs so I'm getting the error message "invalid argument". It is very possible that my foundation is off in regards to how I went about setting up these variables in the first place since I am still so new to Power Apps and am trying to get my head wrapped around how global and contextual variables work. If we were to start from scratch what would be a better way to approach what I am trying to achieve as stated in my original post?
Thank you,
Teresa
Hi Sik,
I just realized I was supposed to enter the formulas into the Visible property, not the OnSelect property so I restored my OnSelect formula for the Edit icon to EditForm(frmRequestVE);UpdateContext({ReqEditlbl:true}) and entered tabRequest.Selected.Value="Request" && ReqEditlbl=false into the Visible property of the Edit icon. It generated 3 errors. I have attached a png for your review. Same question as before, should I be approaching the variables for the 3 tabs in a different way?
Thanks again for your help!
Teresa
Hi @tagustin2020 ,
That's ok, so these tabs are all buttons, and the tabrequest is the name of request button, right?
I would suggest you create a variable to reflect the tab selection in OnSelect event of four Tab buttons.
Set(varSelectedTab, "Request") // tabRequest.OnSelect
Set(varSelectedTab, "Designer") // tabDesigner.OnSelect
Set(varSelectedTab, "Model Shop") // tabModelShop.OnSelect
Set(varSelectedTab, "Comments") // tabComments.OnSelect
Then, modify the visible property as follows. (Just take RequestTab as an example)
varSelectedTab="Request" && ReqEditlbl= false //EditIcon.Visible property
varSelectedTab="Request" && ReqEditlbl= true //SaveIcon.Visible property
varSelectedTab="Request" && ReqEditlbl= true //CannelIcon.Visible property
Hope this helps,
Sik
Hello Sik,
Thank you so much for your guidance! I wouldn't have been able to figure this out without your help. Here are the formulas that ended up working for me in the sense that each set of edit/save/cancel icons is only visible when its tab is clicked, that the Edit and Save/Cancel icons toggle correctly depending on which mode I am invoking and finally that the edit/save/cancel icons are only visible to app admins when the Designer and Model Shop tabs are clicked.
Request Tab:
OnSelect: Set(varFormTab, "Request")
Request Tab Edit Icon:
OnSelect: EditForm(frmRequestVE);UpdateContext({ReqEditlbl:true})
Visible: varFormTab="Request" && If(ReqEditlbl=true,false,true)
Request Tab Save Icon:
OnSelect: UpdateContext({ReqEditlbl:false});SubmitForm(frmRequestVE);ViewForm(frmRequestVE)
Visible: varFormTab="Request" && If(ReqEditlbl=true,true,false)
Request Tab Cancel Icon:
OnSelect: UpdateContext({ReqEditlbl:false});ResetForm(frmRequestVE);ViewForm(frmRequestVE)
Visible: varFormTab="Request" && If(ReqEditlbl=true,true,false)
Designer Tab:
OnSelect: Set(varFormTab, "Designer")
Designer Edit Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,false,true)
Designer Save Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,true,false)
Designer Cancel Icon:
Visible: varFormTab="Designer" && isAdmin && If(ReqEditlbl=true,true,false)
Req Edit Label (only 1 label is needed for all the sets - I toggle the Visible property to off/false once I am done testing):
Text: If(ReqEditlbl=true,"Save","Edit")
The Model Shop formulas are the same as the Designer formulas with the exception of the tab name. I am attaching a document that includes other fine tuning details in case anyone who happens upon this post is interested in taking a look.
Again, thanks so much. I really appreciate your taking the time to help me.
Kind regards,
Teresa
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