cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

User.FullName() is not return consistent information - sometimes Forename Surname sometimes Surname, Forename

I am working with a colleague and we see inconsistent behaviour with User().FullName.
When I’m the last person to update/publish the app - the function User().FullName shows “Dan Hibbert”

When my colleague is the last person to update/publish - the function shows "Hibbert, Dan"


It's like it's showing DisplayName from AAD rather than Fullname.

Has anyone else see inconsistent return values for User().FullName ?

In our office settings, a difference we could see was Display Language for me was English (United Kingdom) and his was English (United States) but this may not be related!

 

9 REPLIES 9
Phineas
Community Champion
Community Champion

How does your organization log-in to your devices/system?

If you drop a text box on the screen and type User().FullName in it what do you and your colleague see when you log in independently?

 

You should each see your own AD UserName. That same name should appear associated with any log-ins you attempt or changes you initiate, unless you just happen to both be named Dan Hibbert and the naming conventions are an attempt to avoid identity duplication in the environment. 🤔

Anonymous
Not applicable

We login with username/password 

It's very odd - yes - we have a sample app - when I was the last person to save and publish then (for me) it would show Forename Surname and the same for him.   When he saved and published the app, it changed to Surname, Forename.

 

Then he observed that he edited the app, it would be in Forename Surname but in view mode would show Surname, Forename.


In AD - Our DisplayName field is in Surname, Forename format and FullName is Forename Surname.  It's like User().FullName is randomly choosing which field to pull out.  

 

Have tried to change to another AD field as your source content, if one is available to you; another 'type' of name field or the email field? Drop a text box and try those fields to see if their is in odd behavior with that content? At this point is process of elimination.

@Anonymous 

Use the email field.  It is less prone to variation.  To remove issues with upper or lower case, wrap the value with Lower() or Upper() to achieve consistent results. 

This issue has now been fixed. Previously we used to rely on the user token information. But we had to switch the library we used for authentication as per Azure guidance, which resulted in First name, last name missing in the token and we were falling back on display name. But now we have made it consistent and rely on getting the information from Graph directly and then show you FirstName LastName consistently in all players and studio.

Hi @sagarbakliwal 

 

Thanks for the confirmation that PowerApps now shows "FirstName LastName" when getting User().FullName.

 

However, this does present other inconsistencies, especially with the "Office365Users" or "Office365Groups" connectors - these connectors both seem to return the Users "DisplayName".

 

We have rare occasions where the "DisplayName" in the Office 365 User Profile does NOT equal "FirstName LastName" (e.g. if there are 2 "John Smith" Users, they will add the Middle Initial to the DisplayName to distinguish them - "John A Smith" and "John B Smith".

 

So now, the "Username" given in the Group membership, and the "Fullname" that PowerApps has access to do not necessarily always match.

 

Shouldn't the PowerApps User() function be able to give us BOTH "FullName" and "DisplayName"?

OR, can't the Office365Users and Office365Groups connectors also provide the "FullName" property?

 

This is the problem with so many distributed development teams working on different connectors - there's no consistency!

 

I don't mind which you do, but can we please have some consistency?

Hi all,

Email addresses are unique while names are not, hence my suggestion above. 

Hi all,

Email addresses are unique while names are not, hence my suggestion above. 

Unfortunately, email addresses are not always consistent either, especially with Guest Users and "alternate email" addresses.

 

The simplest and most straight forward thing to do is for PowerApps to have access to the DisplayName - PowerApps is the odd one out in returning "FirstName LastName" - all other User related functionality returns the "DisplayName"...

 

@sagarbakliwal - Are there any plans for the User() function to give us the "DisplayName" that is in Office User Directory?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Results posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Top Solution Authors
Top Kudoed Authors
Users online (2,407)