Hi all,
This is my second app build and excited about Power app:)
Wondering if my IF formula used to combine 2 conditions are accurate for DisplayMode. Looking to make it read only once it is Approved or Rejected. (or Should I use Switch?)
This is for a ticket review screen.
1. If it is ABC or XYZ who is reviewing
2. If ABC or XYZ choose Approved or Rejected, then make the fields as view only, else they should be editable.
my formula:
If(User().Email="abc@12345.com" || "xyz@12345.com" && ThisItem.'Lead Review Status'.Value="Approved"||ThisItem.'Lead Review Status'.Value="Rejected", Parent.DisplayMode.Edit, Parent.DisplayMode.View)
PLEASE LET ME KNOW!
Best!
Solved! Go to Solution.
Ok, yes that's good, that should cover that, now you are checking for a static email address so we need to make sure case-sensitivity is not an issue, as Abc@ and abc@ are two different cases and would not be considered equal, so we use the Lower() function to convert all of them to lowercase only.
Additionally, you have changed your status conditions again, so let's be clear on this and add another condition, as the way it currently is, if anyone else but abc/xyz is looking at it, they will be able to edit, so we can update it as follows:
If(
// If status, then make it view only
(ThisItem.'Lead Review Status'.Value = "Approved" || ThisItem.'Lead Review Status'.Value = "Rejected"),
DisplayMode.View,
//if approver and status is not one of the two statuses, then edit
(Lower(CurrUser.Mail) = Lower("abc@12345.com") || Lower(CurrUser.Mail) = Lower("xyz@12345.com") )
&& Not(ThisItem.'Lead Review Status'.Value = "Approved" || ThisItem.'Lead Review Status'.Value = "Rejected"),
DisplayMode.Edit,
// otherwise, under all other conditions make it view-only
DisplayMode.View
)
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Heya!
Yeah you were so close 🙂
The way you currently ahve it as one long && || means that if Any of the Ors are true then the rest are ignored, but not to worry, we can wrap them in brackets and that will help separate them into sections of logic:
If(
// (If User is X or Y) AND (status is not approved/rejected) then make it edit
(User().Email="abc@12345.com" || User().Email="xyz@12345.com")
&&
!(ThisItem.'Lead Review Status'.Value="Approved"||ThisItem.'Lead Review Status'.Value="Rejected")
,
Parent.DisplayMode.Edit,
// (If user is Not X or Y) OR (status is approved/rejected) then make it view
Parent.DisplayMode.View
)
Cheers,
Sancho
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hi @iAm_ManCat thanks for the super quick response.
However it still doesn't work for me 😞 The formula makes the field view only.🤔
If((User().Email="abc@12345.com" ||User().Email="xyz@12345.com" && !(ThisItem.'Lead Review Status'.Value="Approved"||ThisItem.'Lead Review Status'.Value="Rejected"), Parent.DisplayMode.Edit, Parent.DisplayMode.View)
The Lead Review Status for this example was "Unassigned". So it should have let me edit it cosnidering I am abc@12345.com 😶
Thanks
You are missing a closing bracket closing after the xyz email in the above formula,
also my apologies, I didn't see you had referenced parent for displaymode, which you did not need to and the checking of email addresses is case-sensitive so if you are Abc@ but we are comparing abc@ then that will return false, so I have included wrapping the email address in the Lower function (assuming that you will replace abc@ with a lowercase email representation of your email addresss)
If(
// (If User is X or Y) AND (status is not approved/rejected) then make it edit
(
Lower(User().Email)="abc@12345.com" || Lower(User().Email)="xyz@12345.com"
)
&&
!(
ThisItem.'Lead Review Status'.Value="Approved" || ThisItem.'Lead Review Status'.Value="Rejected"
)
,
DisplayMode.Edit,
// (If user is Not X or Y) OR (status is approved/rejected) then make it view
DisplayMode.View
)
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hi @iAm_ManCat thanks for the response! But, unfortunately it still doesn't work for some reason. I also created a collection of the individuals and tried combining, but to no avail. 😞 Also used Switch function. Nothing works .
If((CountRows(Filter(LeadAppCol,Approvers.Email = CurrUser.Mail))>0) && !(ThisItem.'Lead Review Status'.Value="Approved" ||ThisItem.'Lead Review Status'.Value="Rejected"), Parent.DisplayMode.Edit, Parent.DisplayMode.View)
also tried this:
Switch((User().Email="abc@12345.com"||"xyz@12345.com")) && (ThisItem.'Lead Review Status'.Value="Unassigned"||ThisItem.'Lead Review Status'.Value="Review in progress"), Parent.DisplayMode.Edit, Parent.DisplayMode.View)
Switch function wouldn't apply in this case and the parameters are wrong in the example you gave anyway.
Let's take a step back and look at the issue.
Make a label, make it's text value:
User().Email
Make another label, make it's text value:
"abc@12345.com" (or whatever you are checking)
Now a third label:
User().Email="abc@12345.com"
and if that is false, then that is the issue, as I likely think that your User Principal Name for your account (ie the name you log into your computer/office365) is different from your primary SMTP email address.
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hi @iAm_ManCat You're right. there are 2 diff email domains my co uses.
To solve that:
1) I created this in the App on Start Function and created a collection of Lead Reviewers separately (abc@12345.com +xyz@ 12345.com)
Set(CurrUser,Office365Users.MyProfile());
ClearCollect(IdeaAppCol,'Project team Approvers');
ClearCollect(LeadAppCol,'Lead Approvers')
2) For my Review Screen, I tried this:
please let me know where I'm going wrong, I'd like to correct it and learn pls
If(
(CurrUser.Mail = "abc@12345.com" ||CurrUser.Mail = "xyz@12345.com" )
&& (ThisItem.'Lead Review Status'.Value = "Approved" || ThisItem.'Lead Review Status'.Value = "Rejected"),
Parent.DisplayMode.View,
Parent.DisplayMode.Edit
)
Ok, yes that's good, that should cover that, now you are checking for a static email address so we need to make sure case-sensitivity is not an issue, as Abc@ and abc@ are two different cases and would not be considered equal, so we use the Lower() function to convert all of them to lowercase only.
Additionally, you have changed your status conditions again, so let's be clear on this and add another condition, as the way it currently is, if anyone else but abc/xyz is looking at it, they will be able to edit, so we can update it as follows:
If(
// If status, then make it view only
(ThisItem.'Lead Review Status'.Value = "Approved" || ThisItem.'Lead Review Status'.Value = "Rejected"),
DisplayMode.View,
//if approver and status is not one of the two statuses, then edit
(Lower(CurrUser.Mail) = Lower("abc@12345.com") || Lower(CurrUser.Mail) = Lower("xyz@12345.com") )
&& Not(ThisItem.'Lead Review Status'.Value = "Approved" || ThisItem.'Lead Review Status'.Value = "Rejected"),
DisplayMode.Edit,
// otherwise, under all other conditions make it view-only
DisplayMode.View
)
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Hi @iAm_ManCat unfortunately it still doesn't work. This logic should be working but it isnt 😞 I'll try again and confirm if I get the desired result. Thanks for your inputs
Could you copy paste what you have currently so that I can try and help?
@iAm_ManCat |
My blog |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
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