I have developed an app that is very close to going live within my company.
What happens, is that people raise a report type ticket that is then viewed by others. I need to restrict editing access to only the users that are listed within the ticket. All others can view. The users will change depending on the ticket type. Can someone help me to implement this? I have not completed the Flow as yet. I wanted to complete the app first.
Solved! Go to Solution.
So if you are comfortable with the obscurity approach then the way to do this is to create a People/Groups column in the list and set it to allow multiselect. When a ticket is created add all the people who should be able to edit the ticket to that column. I believe you said this would be based on the type of ticket. Next add the following to the OnStart of the app.
Set(userEmail,User().Email)
This will create a variable with the user's email when the app starts.
Finally, whenever you navigate to a View or Edit Screen check to see if the user's Email is in the People/Group column you created and Navigate to the appropriate form. You can do that with code like this
Select(Parent);If(userEmail in ThisItem.EditAccess.Email,Navigate(EditScreen,ScreenTransition.Fade),Navigate(ViewScreen,ScreenTransition.Fade))
How you do this tends to be different depending on the data source involved. What Data Source are you using? Also is this a flow or a Power App? If its a flow this would be better posted in the Power Automate forum.
My data source is Sharpoint. It is a powerapp. I will be adding a flow to this after so that emails can be sent to the correct users.
Power Apps doesn't provide a security layer, so if you are using SharePoint as your data source your only choice is to change the item level permissions on the item to match the restrictions you want to put in place. This is done using HTTP REST calls, which are normally implemented using a flow.
Another possible alternative is to filter the Power Apps interface so that the affected users only see View or Edit forms for records based on the current login. This will accomplish what you want in the Power App, but isn't really security since the users will still have full access in SharePoint or if they create their own Power App on the SharePoint list.
Hi @Pstork1
I would first like to thank you for your help. I do believe that you have the answer for me there but I am unsure of what I need to do.
I would like to add that none of the other users even know what Powerapps is. They also would not have a clue how to get to site contents to find the sharepoint list once I make the app live. There is only around 20 people that will be using the app. So I dont really have any worries about the security side of things that you mentioned.
So if you are comfortable with the obscurity approach then the way to do this is to create a People/Groups column in the list and set it to allow multiselect. When a ticket is created add all the people who should be able to edit the ticket to that column. I believe you said this would be based on the type of ticket. Next add the following to the OnStart of the app.
Set(userEmail,User().Email)
This will create a variable with the user's email when the app starts.
Finally, whenever you navigate to a View or Edit Screen check to see if the user's Email is in the People/Group column you created and Navigate to the appropriate form. You can do that with code like this
Select(Parent);If(userEmail in ThisItem.EditAccess.Email,Navigate(EditScreen,ScreenTransition.Fade),Navigate(ViewScreen,ScreenTransition.Fade))
Hi @Pstork1
I currently have 'Raised By', 'Raised Against' and 'CC' columns. These all have users and will ultimately be the people that I need to edit the tickets raised. All other users should be able to view these tickets. I am sorry that I am not giving you all of the info at once. I am just not very sure what I am doing. This is my first app.
Kevin
The solution is the same. Just change the IF() statement to check all three columns with an 'OR' like this
Select(Parent);If(userEmail in ThisItem.'Raised By'.Email || userEmail in ThisItem.'Raised Against'.Email || userEmail in ThisItem.CC.Email,Navigate(EditScreen,ScreenTransition.Fade),Navigate(ViewScreen,ScreenTransition.Fade))
Your field names might be a bit different, but this is the basic format.
Hi @Pstork1
I have added the first part to the On Start of the app.
Where do I add the the second bit of Formula? Do I add it to the OnVisible section? If so, how do I add it to Formula that is already in OnVisible
Are you selecting the records for View/Edit from a Gallery? If you are then this goes in the OnSelect for the record in the gallery
It basically needs to go wherever you navigate to the View or Edit screens.
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