Showing results for 
Search instead for 
Did you mean: 

SharePoint Choice List Missing

I wanted to create a flow that would change the "Status" field from 'Active' to 'Filed' once the user puts in an Issue End Date (because the status field is not on the power app form). However, the Status Field (which is a choice list with 2 choices: Active and Filed) was not available in the Update Item fields in the flow.


Is that intentional? I knew we couldn't use managed meta-data or people fields, but didn't hear anything about choice fields not being available for update.


Thank you in advance,


Status: Completed
Level: Powered On

You can now choose to update a SharePoint list item choice field in a Flow, but it crashes!!!

Level: Powered On

@RKushner, how is it crashing? Do you have any screenshots or error messages? 

Level: Power Up

@RKushner - are you encountering a known issue mentioned near the end of this article?

Level: Powered On

Yes, but I tried the workaround indicated in the article and it did not work for Logic Apps. Then I tried the work around in Flow, and it did work there!!!


The error says "BadRequest", and then:


  "message""A value must be provided for item.\r\nclientRequestId: bcdf0168-3a58-4d70-9722-abfe7398b7d8",


but values were provided for all fields. And when I remove the update to the choice field, the Logic App works fine. And when I try the workaround to delete and recreate the list item update, the error is unchanged.




Level: Powered On

Though this action works now, ANY CHANGE to a List that has a Choice Column used in a Flow, even if that Choice Column is not used in the Flow, just a field in the List, blows up the Flow.  For instance, if I delete a Choice Column from a list, every Flow that depends on that list and uses the Update List Item action stops working.  The only way I have found to fix them is to literally delete and recreate all the Update List Item actions in each Flow.  This is a TON of work.  


I could understand if the List Column changed (deleted for instance) is used in the Flow Action, obviously that would have to be fixed.  But when the List Column is not used in the Flow, it shouldn't break the Flow.  It's really frustrating because you don't realize this issue likley until you've created a lot of Flows.