Hi,
Not sure if I've raised this in another message but have now identified what seems to be the cause of why the PowerApp that uses Office365User connector to establish the Manager and Managers Manager who designated for the use in SAP and AD
The app relates to our HR department for job role changes, salary increase and other HR processes.
The manager or managers manager have to raise the query for the user who they manage. If your not then an error message is displayed.
The issue is some managers are gettign this error message even though in SAP / AD they are the manager??
The only discrepancy I could see was in AD the Email field had the email in upper case. So AAnother@test.com. Those that didn't have this issue the email was aanother@test.com.
To test this theory I had the Email, field in AD, amended to be lower case. And they could access the app with no issues.
How can I make the app see upper case AD Email as loser case AD emails?
I've tried
and
But it doesn't change the format??
I'm also trying to get the AD side to default to lower case Emails but I'm not holding my breath for that 😊
Solved! Go to Solution.
I think you need to use lower(lower()) in your first formula. You are casting the email you are submitting to Office 365 users to all lower case, but you aren't converting the .mail address of the manager. That's why the format of the output isn't changing.
Lower(Office365Users.Manager(Lower(EmployeeValue.Selected.Email)).Mail)
I think you need to use lower(lower()) in your first formula. You are casting the email you are submitting to Office 365 users to all lower case, but you aren't converting the .mail address of the manager. That's why the format of the output isn't changing.
Lower(Office365Users.Manager(Lower(EmployeeValue.Selected.Email)).Mail)
Hi @Pstork1
Thank you for your response.
I've used your formula and it does display the Email in lower case.
I still have the issue of the app not recognising them as the users manager??
I still believe it is connected to the Email field format in AD. As I asked for one of the users to have the Email changed to lower case. They can now access the app. The AD Administrator is not keen on converting all formats to lower case and thinks the app should handle this.
The error message becomes visible under the below conditions
I've made the Global Variable _userEmail read lower case from the App, OnStart function
Is there anything, anywhere else potentially I've missed??
The system is going to check against Azure AD (AAD), not on-premises AD. The case of the email shouldn't make a difference in my experience. I would double check that the manager field is getting synced correctly to AAD. Also verify that your emails are the same as your User Principal Names (UPN). They aren't in all organizations and its actually looking up the UPN not the email.
Also, the error message would be there because you are logged in as chpclark but trying to submit as a manager. That isn't because you can't retrieve who the manger is. Its because Power Apps doesn't support security impersonation. You can't submit something as a manager when you aren't that manager.
Hi,
This is where I'm a bit at a loss??
When looking previously I noticed that not all the formats of the emails where the same (UPN, Email, and On-Premises user Principal name.
When comparing the users who could access the app to those that couldn't the Email field was the common dominator in this.
So if the On premises user principal name field format isn't the same as the Email field format could this cause confusion??
Hi,
Another user who as had the Email field changed from upper to lower can now access the app.
Looking at their Azure account all fields with email are all lower case.
Should these, as best practise, be the same format (Upper or Lower)
Getting confused now on how I can make the app accept these irrespective if upper or lower??
If you are talking lower case vs upper case that shouldn't matter for finding the manager. But the UPN and the email can be completely different values in some organizations. This is particularly true if the org uses multiple email domains. But if you're org is syncing on-premises AD with AAD, which they should be, then the UPNs should be the same in the cloud or on-premises.
For getting the manager it shouldn't matter what the case is. But if you are using the manager email in a condition then those are case sensitive. Can you be more specific about the actual error or problem you are seeing? Where in the app is it causing an issue? Is it that you aren't finding the manager for the ones with alternate case? or that the manager that isn't all lower case isn't working in your code?
Hi,
It seems that the users whose Email is upper case are getting this error. If I get those changed to lower case then they can access the app.
It's at the initial stage of starting a new request
This is the formula to make the error message display.
Datacardvalue8 = Manager
Datacardcardvalue98 = Manager's Manager
The names as Mangers 1st and 2nd are the Managers and set in SAP and AAD. I know the error message shows as I'm not the manager but this is what they are getting also.
Here the managers email fields are different formats.
If the format for the Email field is changed to lower case does this set the automatically set the UPN to lower case??
OK, I get it. The problem is that an IF() using an equals is a case sensitive condition. That's why its not working. What you need to do to fix it is put the Datacardvalue8.txt entries in the IF inside a tolower() function. That should take care of the problem. I would suggest using toLower() when you create the _useremail variable too.
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