Hello
I have a powerapp form. I wanted to hide 1 of the fields from the user or make it non-editable but make it show and editable for the users manager. So the process is:
1) User fills in mandatory fields in form
2) 1 or 2 fields would be hidden (preferred) or non-editable for the user in the form
3) The user submits the form and the manager can go back and see the hidden fields and add a value to it
I tried to change the field to read only mode, but then the manager cant edit it.
are there anyways to do this? I had saw some posts about filtering by user roles and permissions which but Im still looking at the best options.
Maybe I could add a filter so if the user belongs to a certain permission group, then hide a field? if not show it
OR the opposite would be better? Make the field hidden and non-editable by default but if then filter it so if the email address is a managers it will show?
Thank you!
Solved! Go to Solution.
hi @Anonymous
Sorry for the late reply. How do I do step 9 or where/what do I write on the data card?
9. Then you can bind your fields visibility to isAdmin
Sorry about the picture. I have uploaded some more pics in one below. Im not sure what the error is. Maybe after I bind it?
Thank you, once again.
Keep in mind with all of this that you are creating security through obscurity. The fact will still remain that if a user can edit columns of a SharePoint list, they can edit them all. The fact that you Hide a field from users in PowerApps does not preclude that they can't still get to the information directly in the SharePoint list. Just wanted to make sure that was aware.
Now, the suggestion that @Anonymous suggests is pretty much spot-on. If you want to control the visibility of a DataCard you can do so with the Visible property of the DataCard.
1) The super simple - Visible: (User().Email="someone@xxx.com") only that person will see the datacard.
2) The more flexible but more complex - Create a Role/Access (Access Control List - ACL) in SharePoint and provide names and roles there that can access. I will state one of the processes I use often for this...
Step 1 - Create a SharePoint list for your ACL
Call it what you want (I'm calling it AppACL in this scenario) and put it wherever you want. I'd recommend that general users ONLY have read access to the list - they must have at least that permission.
Step 2 - Put the following Columns in the SharePoint AppACL list (as an example - you can add other columns for other aspects of the role):
UserEmail Text Column (you can rename Title to this if you want, just remember it is still technically "Title")
HasManagerRole - A Yes/No column
Step 3 - Add a record (or more) in the SharePoint AppACL list with the email address of the people you want to have access. Set the HasManagerRole to Yes for them. (By nature of this solution, you don't have to add people who would NOT have a manager role, only those that do).
Step 4 - In your PowerApps app, create a connection to the AppACL list.
Step 5 - In your OnStart (best place for it, but you can do elsewhere if necessary) place the following Formula:
Set(MyACLprofile, Lookup(AppACL, Title = User().Email)) //remember from above if you renamed Title to UserEmail, it's still title. If you added another column for the email address, then use that instead of Title
Step 6 - Anywhere you want to control a property based on the permission in the ACL, use the formula:
MyACLprofile.HasManagerRole
So, for your needs, on the DataCard for the field you want to hide from everyone except those with access, set the Visible property to (MyACLprofile.HasManagerRole)
That's all there is. You can now control the datacard visibility (and any other control you set this on) from your SharePoint ACL list.
Hope this helps clear it up.
1. your error results from the last semicolon in your App.Onstart
2. you have to write your variable isAdmin to the property called Visible of your datacard
Thanks! @RandyHayes and @Anonymous for continual help
Quick Question.
Does this warning matter? Or anyting else look weird?
This is a standard Delegation warning. The formula you have is not delegable on the DataSource. When you see these warnings you have to take note and consideration of the potential size of your list.
If your list will be relatively small and will never grow to thousands of records, you can ignore the warning.
In this case of an ACL list, you probably will never grow the list that large and you can safely ignore it.
In other cases, you need to plan for delegation issues...which is a whole other topic that has many postings about on this forum.
what about the red squiggly under the =
I am getting that too and it says it's an invalid argument type
hello @Anonymous
the formula should be 'UserEmail.Email = User().Email))' This fixed the error for me 🙂
thanks so much! that made the error go away, but I am not having luck with it working. I am trying to use this to make the displaymode edit or view.....it will only view. I think it's not seeing the list,
Not sure what I am missing. here are my formulas
on start: Set(MyACLprofile, LookUp('Lead Producer', Presence.Email = User().Email))
Displaymode: If(MyACLprofile.HasManagerRole,DisplayMode.Edit,DisplayMode.View)
the list is called Lead Producer and the column is calle Presense.......hmmmmm....what am I missing here?
@tested1 wrote:hello @Anonymous
the formula should be 'UserEmail.Email = User().Email))' This fixed the error for me 🙂
@Anonymous
If it's always View mode, that means that your If statement is always False. So, there are one of two issues - either there is a problem with the Formula where you lookup, or there is an issue with the Datasource record.
So, easy one first...verify in your DataSource that you really have the HasManagerRole set to Yes.
Next, try putting a label in your App somewhere and set its text propery to:
MyACLprofile.HasManagerRole
With that you will see the exact value that is coming back through your lookup.
See if that helps identify the issue for you.
Thanks and a great idea! - I created the text box and it shows false regardless of whether make the "HasManagerField" field yes or no.... so something is wrong with my formula. It is always false.
here is my forula
Set(MyACLprofile, LookUp('Lead Producer', Email = User().Email))
Lead Producer is the list name
Email is the text field where I have my email
I have tested that user().email returns my email , so they are equal.
not sure what I am missing - I have permissions to vies the Lead Producer list....everyone does.....
thanks for all your help - I know I'll get this eventually. any more help would be greatly appreciated though 🙂
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