Showing results for 
Search instead for 
Did you mean: 

Enable null function to clear a previous value from a person or group field

 When using the Update Item action for a SharePoint List, it is not currently possible to clear a value that has been previously set in a Person or Group type field (Claims). Attempting to do this currently causes the Flow to fail, with a "Badgateway" 402 error, arising from a "user does not exist" 400 error.


Please enable the dynamic content expression to allow use of the Null() function to clear previous content from ANY field type, including person or group claims fields.

Status: New
Regular Visitor

Just going to second this since it is inconvenient in the extreme. I like the suggestion of using null() to generally clear all field types for consistency. I think developing another SharePoint action other than Update Item should not be needed for this.


@ONYXJas You can use the REST API to do this in Flow using a POST request and setting the field to -1, if you need a work around badly.

Not applicable

Yeah, this problem really put a damper in my development this week. 


Regular Visitor

As mentioned by the two commentors above, this is a serious shortcoming for something that should be inherent in the system. It's a shame such a simple piece of functionality has been so slow to be implemented. You are basically making some of the most powerful functionality (Person field as a column) useless. Please spend less time adding new triggers and more time perfecting base functionality.

Frequent Visitor

Which is even worse, you can't pass a blank value using expression to Person field. 

Advocate I

it's been 2 YEARS - will this be reviewed and fixed?

Regular Visitor

This need to be fixed in forms and in flow

Regular Visitor

Absolutely agree with @jamesbarker . Let's get base functionality working .Not able to nullify a person field should be basic functionality. It's been over 2 years since this idea was first registered. Any updates @PowerAutomate team??

Advocate I

I just stumbled upon this issue... would be great if the function could work as expected.


Any update?

Advocate IV

...not that I'm aware of 😞

Advocate I

In the context of GDPR this will be a dealbreaker if not implemented soon!