Unanswered

Flow Status Error 400 - "The required field \"Permission Level Requested\" data type is not supported

(1) Share

Report

Posted on by lostgical

Trying to connect to an Access Request list using the "When an item is created of modified" trigger action, but getting the 400 error:

"The required field \"Permission Level Requested\" data type is not supported

I'm able to open the list by URL in browser (example: "https://[site URL]/_api/web/lists/getbytitle('Access%20Requests')/items?$select=RequestedFor, Status") but Flow fail at this trigger action.

Any ideas/approach to try much appreciated!

Categories:

Using connectors

All responses (7)

Answers (0)

Sort by

MarkStokes 561 on at

Like
a
(0)

Report
Copy link

Link copied!

What SharePoint field type is ‘Permission Level Requested’?
ScottShearer 25,331 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Can you please post a screen shot of your Flow as well as posting a screen shot of the permission level required column configuration please?

Scott
lostgical 45 on at

Like
a
(0)

Report
Copy link

Link copied!

This is the "Access Requests" list, my guess that the SharePoint field type is ‘Permission Level Requested’ might be the Person or Status fields? I can't change neither, this is the Access Request list...
lostgical 45 on at

Like
a
(0)

Report
Copy link

Link copied!

Please see the psot above for the list columns, this is the standard Access Request list. Below is the Flow error:
Mahavir 16 on at

Like
a
(2)

Report
Copy link

Link copied!

Go to list settings for the Access Requests list, select the 'Permission Level Requested' column to change, select 'no' for required property. I tried this and works. Had similar requirement like what I am guessing you had - automatic access provisioning.
BryanOReilly 3 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for this!
zylantha2 103 on at

Like
a
(0)

Report
Copy link

Link copied!

For future reference, I have had this same error on a lookup field where the user did not have the required permissions on the lookup list. Users who had "Limited Access" to the lookup list had no issues, however a user who had not been granted at least "Limited Access" would get this failure in the workflow.

Granting everyone read only permissions to the lookup list resolved the issue for us.