cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to update just changed field for SharePoint items

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.

Comments
Level: Powered On

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.

Level: Powered On

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

Level: Powered On

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.

Level: Powered On

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.

Level: Powered On

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.