Solved: Not all columns show in SharePoint Update Item

jerrym · ‎01-18-2017

I'm trying to use the SharePoint Update Item action to update a list item. I see that the action lists columns to be updated and makes them all required (whether you want to update them or not). But it does not list 'all' columns and there is no option to add the missing columns. However, I do see the missing columns in the 'dynamic' content that is availble for update values.

Are some column types no supported in Update Item? Is there some attribute in the list settings that will make the columns appear/not appear in an update item flow?

Thanks,

v-yamao-msft · ‎01-18-2017

Hi Jerrym,

As far as I know, Person/Group, Lookup, Choice, Calculated, Managed Metadata, External Data column types are currently not supported in the action “SharePoint Online--Update item” yet. So you are not able to update these columns, but you can use these columns’ value to update other available columns, so you could see these columns in the “Dynamic content”.

Could you show me your column types in your list?

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

v-yamao-msft · ‎01-18-2017

Hi Jerrym,

As far as I know, Person/Group, Lookup, Choice, Calculated, Managed Metadata, External Data column types are currently not supported in the action “SharePoint Online--Update item” yet. So you are not able to update these columns, but you can use these columns’ value to update other available columns, so you could see these columns in the “Dynamic content”.

Could you show me your column types in your list?

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

jerrym · ‎01-19-2017

No need, that answers my question. It's not a very useful action with this limitations.

Thanks,

JM

Anonymous · ‎07-09-2017

That's very unfortunate.

There is a problem/limitation where if I'm setting up alerts based on status changes (e.g. moving from 'planned' to 'scheduled'), the only way to do that is to set a 'when item updated and this status field = scheduled - send an alert'. However, this means that any time anything on the entire item is updated whilst the status field = scheduled, what is considered a duplicate alert is sent out.

The workaround posited here where you apply a condition to check the status value before the item was updated and if it matches - no alert is sent. If it doesn't match (i.e the status value has been updated), then the alert goes out.

That workaround, is rendered useless - due to this limitation.

So what I'd consider a widespread requirement is not possible with M$ Flow and therefore, the entire process is takin out of the MS environment and handled elsewhere.