Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Using Flows
Unanswered

BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

(0) ShareShare
ReportReport
Posted on by

When I run an approval flow that is triggered by a new row being added to a list, it fails at the second step which is "Get My Profile".  The error message is: Parsing OData Select and Expand failed: An identifier was expected at position 0.

 

error message.png

This is the step in the flow that is failing:

Flow.png

 

I followed the instructions in this article but with my own table which has different fields to those in the example. https://docs.microsoft.com/en-us/power-automate/modern-approvals  

Any help would be gratefully received as I am not sure how to fix this!

  • d-bear Profile Picture
    2 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    I realize this is an old thread, but I ran into the same issue following the same tutorial. The only way I got it to work was to remove all fields from the Select Fields section of the Get my profile (V2) action. I found that if you leave this field blank, all possible parameters are automatically submitted. In other words, all of the fields like ID, Title, Start Date, End Date, etc. will still be available in the next step. A more elegant solution may be needed for larger projects, but for those of us who are just learning, this solution works perfectly.

  • JuanMartinez Profile Picture
    2 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    Hello,

     

    I noticed youre using 'get MY profile' but im pretty sure you should be using 'get USER profile v2'.

     

    Let us know.

  • bberndtson Profile Picture
    5 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    Same here

  • HQ-1 Profile Picture
    2 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    Same

  • aristote33 Profile Picture
    2 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    feels like a bug with the workflow action.

    I had the same with 'Get user profile (v2)'.

    Just added another 'Get user profile (v2)' action with the same input and it's working fine.

  • viyer Profile Picture
    48 on at
    Re: BadRequest Error: Parsing OData Select and Expand failed: An identifier was expected at position 0.

    Hi @Lawlessg 

     

    I am also facing the same issue , let me know if you find out the solution.

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

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Markus Franz – Community Spotlight

We are honored to recognize Markus Franz as our April 2025 Community…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,679 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,015 Most Valuable Professional

Leaderboard

Featured topics

Restore a deleted flow