Ability to update just changed field for SharePoint items

[MikaelSvenson]

When adding the "Update SharePoint item" action you have to specify values for all required fields. If you're not changing them you still need to fetch the item first in order to provide values for the fields.

It would be useful if the update SP item action only updated fields you provide a value for, effectivly doing a MERGE.

[Anonymous]

Unless I'm not fully understanding something...this strikes me as critically needed for Flow. Being forced to update required fields essentially backs us into a corner where we could easily be triggering our same workflows again based on fields being "modified" that we didn't even want or need to update. 

[MarkDomansky]

I'd like the ability to only update a single or perhaps couple fields within a sharepoint list item.

The current process is VERY painful, I have to get the existing list item, then update the list item and set all the properties to their old value with just the one or two properties modified as I desired.  This is especially painful for 20-30 property lists.

When updating, consider a default value of "existing value" and only when I add something to the field, or when add a dynamic content does it actually modify the value.

[MarkDomansky]

It's also worth pointing out, if I add a field to a list, this method wouldn't break the flow or the field in the list if I forget/don't update the flow to support that field.

[PFed]

I like the idea of making the default choice for each filed "existing value".  This means I could just use update the field(s) that I want to.  It is a lot of trouble and annoyance to have to go in and set each field to its current value.

[roffe_saga]

Please allow option to only update specified fields as to not destroy the items version history.

[harzicn]

I am new to Flow and have only just discovered that the Update Item is an all or nothing thing. In my scenario, I have an approval Flow with a condition to change a single field to a specific value upon approval. In this way I can pass on some information to the submitter only after the approval has been given.

I do not want any of the other fields to change and it does seem a limitation (not to mention a waste of processing and effort) to have to reset all the other fields to their original values manually. Having to update all of the fields in this way also seems to present uncessary oportunity for error and loss of data.

Thanks.

[levijohnson]

I'm just about to write my own custom web service to accomodate for this. So **bleep** annoying. 

[Perry]

I'd like to add that by default each SharePoint field should retain the default value it entered into the flow with. Once you "check" a field it can be updated with a new value. The way it is currently implemented it's ambigous if the SharePoint field is going to keep the value, be cleared, or be reset to a default value. By having it checked, you can expliticly determine if something is going to be updated or not.

[Cabrol]

It lacks usability when you must update all required fields and choice fields that have default values on a SharePoint list item. I know in advanced settings that you can limit fields by a particular view but that itself is problematic. SharePoint Designer completed this task with ease.

[Cabrol]

The SharePoint update item is buggy with using views to filter columns. If any columns in the view change you must delete the step and start over. The step holds on to the column that no longer exists in the view. The step actually holds on to the field data even if the column is deleted in SharePoint.