Unanswered

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

(0) Share

Report

Posted on by Lawlessg

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:

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!

Categories:

Using flows

I have the same question (0)

All responses (6)

Answers (0)

viyer 48 on at

Like (0)

Report
Copy link

Link copied!

Hi @Lawlessg

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

Was this reply helpful? Yes No
aristote33 2 on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
HQ-1 2 on at

Like (0)

Report
Copy link

Link copied!

Same

Was this reply helpful? Yes No
bberndtson 5 on at

Like (0)

Report
Copy link

Link copied!

Same here

Was this reply helpful? Yes No
JuanMartinez 2 on at

Like (0)

Report
Copy link

Link copied!

Hello,

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

Let us know.

Was this reply helpful? Yes No
d-bear 2 on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No