If the column is not a required one, meaning there is no red tag beside the field, then you could just leave the field blank when creating the flow.
Thanks you for you reply.
I thought that was the case. However if you leave them blank when updating a record. they will not be updated at all. That why I was wondering how to remove existing value. I can ofcourse enter a <space> however that I can later on not check wheter this field is empty. I tested this with the Item Update shown below. The empty ones will not be emptied when running this. Only the one at the bottom will get updated.
I have the same question: I am trying to build a Flow that sends an email with options, and if Option "Delete" is chosen, one field is supposed to be emptied. But I can't make it work, so for now I must settle with "update with <space>" but that is not what want to do. Looking forward to a solution 🙂
This is a really old post, but I am trying to do this as well. I do not believe leaving a field blank in an Update Item will remove the contents. No value simply passes over the field and does not update it. Anyone else have this experience?
I've experienced this as well. Leaving it blank simply leaves the data that is in the list and doesn't wipe it. I want to wipe a numerical column from whatever data it contains back to blank each day. Currently I use "0" but my users find it hard to view hte list and would prefer it to be emptied if possible. Is this possible?
To clear the current value from a field when using SharePoint Update item, select the dynamic content option, click on the Expression tab and select the Null function, then click OK. This clears the current value and sets the field to null.
Have you had an opportunity to apply @ONYXJas‘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
Nice one, @KutubK. I'll definetely stash this one in my bag of tricks. I dont know how some of y'all come up with these solutions. If its anything like me, its a very time consuming and cumbersome trial and error process.
I've been looking for hours for a solution to this. I should not have to set up an HTTP Post action just to clear a user/group field. This is an incredibly frustrating limitation, and would like to see some type of update or acknowledgement from MS for this shortcoming. Can you provide any updates on this? We need the ability to clear person fields with the update item action. EVERY OTHER field type you can user null, or -1 for choice fields. I would take either for person fields.
@KutubK Thank you for this post. I've been looking for this for a bit now. I'm new to this and programing, so I have a question on field name in the body. The internal field name in my SP list is Support_Resource and it is displayed at Support Resource Name. I've tried all combinations of this in the Body of the request and I keep getting an error saying "The property 'whatever I usedStringID' does not exist. I've tried the following:
'Support_x005f_ResourceStringID', 'Support_ResourceStringID', 'Support_x0020xResource_x0020NameStringID', 'Support_x005f_Resource_x0020_StringID', 'Support Resource NameStringID', and 'Support_x0020_Resource_x0020_Name_x0020StringID'
All of these return the same error. Any suggestions?
Hi @Bob_Taylor ,
Did you try Support_Resource? Nonetheless if you have this problem again I suggest you put a get items or a when an item is created trigger referencing the list you want to update, then in your update item just set the field you want to update to a dynamic value and search for that very same field from the previous step, after you have selected the field hover over it to see how it is referenced you will find it in ['yourfield'].
Step using when item is created:
Steps using get items (this will add an apply to each):
Three Super User rank tiers have been launched!
Features releasing from October 2020 through March 2021
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!