Power Automate "Update Item" step for SharePoint should not automatically apply column default values to existing list items
The "Update Item" step automatically retrieves the default value for SharePoint list columns that have default values specified and incorporates them into the step. This can corrupt a list by unintentionally overwriting values that already exist in those columns. It is a highly counter-intuitive behavior for two reasons: 1. it does not make sense to apply default values to existing list items, which may already have different values specified; and 2. the "Update Item" step does not otherwise automatically apply values to columns that do not have default values. In my opinion, "Update Item" should not make changes to fields/columns that are not EXPLICITLY configured by the Flow's author.
Anonymous
shared this idea
8 comments
-
Anonymous
commented
Had this same issue happening too and found this thread, then I've managed to find something that at least works for me now.
In the flow for update item it had populated itself with the default value of the columns so each time a calculated value refreshed it changed the other collumns back to the default. But in the flow if I set the values for those to dynamic content and selected the column name as the content it keeps whatever is set in there rather than changing to the default.
-
Sparrowhawk
commented
I had an idea for entirely new connector they could give us: One that allows you to update only select column values on a given item. They've got all the info they need to abstract it away into a friendly connector for us to use.
-
Jason
commented
This exact problem corrupted my list yesterday! I only wanted it to update a single column and it reverted two other status columns to default values after we had manually dispositioned them. The Update Item functionality is useless if it can only be used in lists without default values.
-
Udayan
commented
I agree ! Its time consuming . at blank filed should not be updated . or we should have action to update a single filed .
-
Mike
commented
100% agree! It is tremendously inefficient having to re-populate every column over and over. An alternative option... add a new "Set Field" action that comes with the SharePoint on create/modify connectors
-
Steve Walker
commented
I nearly destroyed some really important data. At the last minute I asked myself, "wait, is this going to clear the content of all those fields?" and yup, it would have.
-
Anonymous
commented
And/Or allow the option to update a field without having to specify the value for every other single field in the list.
-
Artyom
commented
I would suggest to implement "Add field value" user experience. It could make step settings more clear for understanding the step logic.
