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

Announcements

Welcome to the Power Platform Communities
Sign Up for Ask a Community Pro Today!
Share your business problems and get Power Platform leaders' perspectives!
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / {"@odata.type":"#Micro...
Power Automate
Answered

{"@odata.type":"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser","Claims":"i:0#.f|membership| Leave Request Flow

(0) ShareShare
ReportReport
Posted on by zmm14 72

Hi everyone,

 

I'm going crazy after thinking I finally got my leave request right. Hope anybody could help me with any idea.

I discover All leave request are done by me. I have 2 SP List

SP List 1 - Leave request use by employees 

SP List 2 - Leave balances for each employee

After a Leave type is approve, update item on SP List 2, then send an email to the employee that requested the leave.

The SP List 2 is being updated but no email is sent to the employee with their balances.

I also change everything in dynamic content to Modify By and still not working.

What can I do, PLEASE!

 

Im getting {"@odata.type":"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser","Claims":"i:0#.f|membership|

zmm14_1-1634341866078.png

{"@odata.type":"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser","Claims":"i:0#.f|membership|

 

zmm14_0-1634341430387.png

 

Categories:
General topics
I have the same question (0)
  • Verified answer
    Expiscornovus Profile Picture
    Expiscornovus 33,480 Most Valuable Professional on at

    Hi @zmm14,

     

    If you want to use the Modified by field there should be a Modified by Email in the dynamic content. Can you try and use that field instead of the Modified By?

     

    modifiedbyemail.png

  • zmm14 Profile Picture
    zmm14 72 on at

    Thank You! It solve my issue, still encountering others but working on solve it.

  • khyland Profile Picture
    khyland 6 on at

    Unrelated, but I had this error happen suddenly in an approval flow, and the error was resolved by changing the dynamic content "CreatedBy" to "CreatedByDisplayName". Not sure when that change was implemented but wanted to give a heads up in case anyone, like me, wasn't finding any help with that. 

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

News and Announcements

Welcome to the Power Platform Communities
Sign Up for Ask a Community Pro Today!
Share your business problems and get Power Platform leaders' perspectives!

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the December Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
trice602 Profile Picture

trice602 237 Super User 2026 Season 1

#2
David_MA Profile Picture

David_MA 176 Super User 2026 Season 1

#3
Power Platform 1919 Profile Picture

Power Platform 1919 96 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Question for everyone : How are you using Create Text GPT in AI Builder?
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans