I have a simple Flow created, whihch should updated Sharepoint list item field.
List has two column, Title and Value. Title is mandatory field.
Now items is manualy created in the list, with some value for for Title field and Value field being blank.
Whenver new document is uploaded to document library, it is supposed to update only Value column of the list.
However in flow, it is mandatory to select TITLE column value as well
Is these any way to update only Value column without disturbing title field? Really bad design . It was fairly simple in sharepoint designer. (We are instructed to achive this usin FLOW)
Thank you, may be i dint write it clearly.
As i said, I am intrested in updating "key" field only and do not want to touch title value. Even If i want to set it to existing value, i wouldnt know it in every case.
There should have been a way to update single field withough affecting other fields
The proposed solution will work in your case. The trigger step includes all of the original field values, so you can just set the new value to the same as the old value. SharePoint version history will recognize if a value is the same between versions.
My issue is similar, however my problem is when I want to update a single field in a list that contains a lot of fields (30+). The same solution works, but it is very tedious to set each field to its previous value. The user interface slows down, making the process time consuming and error prone.
It would be great if there was the ability to click a checkbox on a field to assign it the same value as it already has. Or have a different action that allows you to just specify the fields you want to update.
if you leave any field blank it will not update this field.
Only Required Fields must be 'update' to same value.
Now about a checkbox it's a really good idea, we can post this
Is this still the case? It seems like a silly workaround. The problem is that when we look at the version history, it looks like flow is changing these fields.
My workaround is to make the fields not required, build the flow and then make them required again.
The flow should allow for a "don't care" state for fields not being updated.
Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @gamoraes‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
Flow Community Manager
Sorry, Unfortunately no, we ended up using old sharepoint desingner workflow. its really not a solution since, exisitng field needs to be modified and end up being part of version history and messing up the Audit system that user changes everything .
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.