web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Bug with displayName v...
Power Automate
Unanswered

Bug with displayName variables in fields

(0) ShareShare
ReportReport
Posted on by 2
Hi folks!
 
Back in April, 2024 I built a flow that pulls the tags from a Team, loops through them to pull the users associated with each tag and then writes the user's display name, email address and tag to a row in an excel file. This was working perfectly in this flow for several months. I needed to do the same for a new Team, so I duplicated this flow and set it up the same way, but now I'm encountering a bug which works as follows:
 
Both the user and the tag have displayName variables that contain the user's full name and the human-readible tag name respectively. This was no issue when I set up the flow in April. However, this time, I set up the flow and when it runs, power automate is replacing the tag displayName with the user's displayName variable so no longer writing the correct information to the row. When I went back to my previous functional one and checked that I had the variables set correctly, it saved the flow and now it is also broken by the same bug.
 
I'm not sure how to approach a fix for this as it seems to be on the backend of power automate. I thought about running a script to code the different variables but there's a learning curve to that which may not be worth it in the end.
 
Any support you can provide with this would be much appreciated.
 
Thank you!
 
Greg
Categories:
I have the same question (0)
  • GV-28112144-0 Profile Picture
    2 on at
    Hi folks!
     
    I have found a workaround for this. In the field that I want the tag name to appear, I can pull the tag display name by specifying the 'current item' in the loop, which is populated from the Get all tags in a Team node and then the property 'displayName' following it. This works as I originally had intended, though is less user friendly for when I plan to share this flow with others in my organization. I still think it's probably important to note the bug for other users and hopefully it's just some quirk of the current version of the API and will be patched sometime soon!
     
    Greg

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 274 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 175

#3
Haque Profile Picture

Haque 166

Last 30 days Overall leaderboard