Not all columns show in SharePoint Update Item

[jerrym]

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 · Accepted solution]

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

[jerrym]

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

Thanks,

JM

[staffsarge]

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.

[efialtes]

@jerrym Please note there are several related Flow Ideas requested you can vote

https://powerusers.microsoft.com/t5/Flow-Ideas/SharePoint-Update-Item-Choice-Field/idi-p/32402

https://powerusers.microsoft.com/t5/Flow-Ideas/Implement-the-feature-to-be-updating-the-quot-Choice-...

https://powerusers.microsoft.com/t5/Flow-Ideas/In-Flow-actions-SharePoint-Update-Item-Allow-access-t...

https://powerusers.microsoft.com/t5/Flow-Ideas/SharePoint-Files-all-fields-not-just-a-few/idi-p/2882

Taking into account the combined number of votes, let's hope Micsofot Flow team will implement this feature soon!

[josy1024]

Im getting a Workaround for writing any Attributes in Document Library from Taxonomy.

grab Value and Attribute ID from Taxonomy store.

Initialize a Variable with the "Attribute Value"|"Attribute unique ID"

eg: Value|133327b0-bbca-402a-8d1b-xxxxxxxxxxx

change the Variable with Your Needs in Flow.

update Document Properties and the MMD column with the Variable.

[Anonymous]

Hi, 

Is this still the case as I have a similar issue. Thanks.

Zeb