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 / Person not populated i...
Power Automate
Answered

Person not populated in two cloned flows (Send an email with options) — works in ~80% of clones

(1) ShareShare
ReportReport
Posted on by 9

Hi everyone,

Issue:
We have several cloned Power Automate approval flows (SharePoint list backend). In ~80% of the clones the Person “ApprovedBy (Claims)” field is populated correctly from Send an email with options (after the user clicks Approved/Rejected/Pending). In two cloned flows the ApprovedBy (Claims) ends up empty on first write and we see one of these at runtime:

  • Failed to retrieve dynamic inputs. Error details: 'Cannot read properties of undefined (reading 'inputs')'
  • Action 'Update_item' failed: The specified user i:0#.f|membership| could not be found.

What we do / expect:

After Send an email with options (single real user in To), we update the item:

  • …ApprovalStatus (Choice)
  • …ApprovedBy (Claims) → want the responder (not the modifier)
  • …ApprovalDate, …ApprovalComment

What we’ve tried:

  • Reading current value: outputs('Get_item')?['body/...ApprovedBy/Claims'] → null on first write.
  • Building Claims from SendOptions… → To (e.g., outputs('SendOptionsCOO')?['inputs']?['to']) → works in most clones, but in the two failing ones inputs is undefined at runtime.
  • Fallback to Editor#Claims works, but that’s the modifier, not the actual responder.

Schema notes:
Person columns are single user, People only; new short internal names; content type mapping is OK. Other role flows with identical structure work fine.

Ask:

  • Is there a reliable token/pattern (still using Send an email with options) to get the responder’s email that works on first write and across clones?
Thanks a lot for any pointers!

Kinga

PAerror.png
Categories:
I have the same question (0)
  • Verified answer
    KF-13030646-0 Profile Picture
    9 on at
    The issue is now resolved. After switching off the new Power Automate designer and rebuilding the affected steps in the classic designer, the functionality started working flawlessly.

    The old designer correctly handles the dynamic tokens and expressions, and the Claims value now populates as expected.

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 Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard