I have a SharePoint list that originally has a multi-choice field in it. I can successfully read and parse the array of values selected in the field and use them in other connectors. However there is a bug that happens that when I try to use the update item action, 1) the multi-choice column doesn't show up to update and 2) Will cause the Flow to fail even with not showing up because Flow will try to automatically set any choice dropdown field for whatever reason. The result is that no Update Item action can be used at all on a list with a multi-choice field because you cannot set it explicity and Flow fails to avoid setting it and tries to set it behind the scenes even though it cannot. See the error below, the update item action is trying to set the value with the array value and failing.
Error: InvalidTemplate. Unable to process template language expression in action 'Update Item' inputs at line '1' and column '2368': The Template language expression 'triggerBody()?['multi_choice_field']?['Value']' cannot be evaluated because property 'Value' cannot be selected. Array elements can only be selected using an integer index.
Known current limitation on create or update sharepoint item -- the following field types are NOT currently supported.
Basically NO multi-valued Sharepoint Fields are supported in Update or Create actions at this time.
And care must be taken in handling Multi-choice fields from a trigger or Sharepoint Get Item(s). For Example if you have a multi-choice person field and attempt to use that field (the Email field within a person field) in a Send Mail action Flow will immediately put that Send Mail into a Apply to Each loop which I believe will then send out x number of emails based on the number of multiple values -- but I have not tested that.
Thanks for your feedback, the issue is confirmed on my side. I agree with @SPMP's thought almost.
Updating multiple choice field of SharePoint list is not supported in Microsoft Flow currently. If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:
I understand that trying it is not "technically" supported (even though I can still iterate over it passed from the initial trigger), but it seems like a bug rather than an enhancement in the fact that not even using the field in the Update Item Action causes it to fail regardless. I'm not entirely sure the backend, but it seems even with the field hidden the action is still trying to set the field to the existing value (in this case an array) which is what is causing the error.
I would think a better way to handle this would be to not show the field in the Update Item Action (like it currently is) and also not try to update it automatically behind the scenes to cause the Flow to fail. This way it avoids trying to do anything to the field and maintains existing functionality.
If this still falls under just supporting multi-choice fields in general then I guess I'll just have to wait. =(
In Flow, it does not matter what you are trying to do, but you will always get to the point when all your plans fail because something that is rather basic is "not supported yet".
Why do we keep throwing time after a product that still can't perform such basic functions???
I know this is an older thread, but for anyone looking for answers here, try this:
You must initialize a string variable, then APPEND TO STRING VARIABLE (not just Set it). When you plug in the value, it will automatically wrap in an Apply-to-Each loop. Add the comma after the value. I found that while my Flow is running, the values appeared in the list but if I went to edit the item properties, it appeared that nothing was actually selected. However, once the Flow completed, I checked item properties again and the choice values WERE selected and looked normal.