# Any way to clear a dropdown field using API or the Power Automate update fields action?

**URL:** <https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902>\
**Category:** Advanced Uses\
**Tags:** api\
**Created:** [May 17, 2024, 12:05am UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902 "2024-05-17T00:05:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdesilva](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.process.st/kdesilva/32/398_2.png) [@kdesilva](https://community.process.st/u/kdesilva)\
**Post date:** [May 17, 2024, 12:05am UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/1 "2024-05-17T00:05:42Z")

</div>

Is there a way to clear a dropdown or multi-choice field using the api? It keeps kicking back at me saying I need to choose one of the options, but I’d like to clear it out similar to hitting the x button manually. @Tarik @Jeff any thoughts? I’ve tried `null`, an empty string, a space, and an empty array to no avail.

```auto
{"error":"The option '' for the select field 'rIo1C9b1A8Ex9VS7XvpMRw' is not valid. Valid options are: 'Approved', 'Rejected – Need More Information', 'Rejected – Request Denied'"}

```

---

<div class="post-metadata">

**Author:** ![Ellie](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.process.st/ellie/32/42_2.png) [@Ellie](https://community.process.st/u/Ellie)\
**Post date:** [May 17, 2024, 8:35am UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/2 "2024-05-17T08:35:50Z")

</div>

@kai this is a bug, I’ve reported it 🙂

---

<div class="post-metadata">

**Author:** ![Panghus](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Panghus](https://community.process.st/u/Panghus)\
**Post date:** [May 27, 2025, 11:54am UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/3 "2025-05-27T11:54:35Z")

</div>

Any news as of when we can expect this to work? 🙂

---

<div class="post-metadata">

**Author:** ![kdesilva](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.process.st/kdesilva/32/398_2.png) [@kdesilva](https://community.process.st/u/kdesilva)\
**Post date:** [June 26, 2025, 10:23pm UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/4 "2025-06-26T22:23:08Z")

</div>

Try using a comma ( , ). This is my current solution and seems to work consistently!

---

<div class="post-metadata">

**Author:** ![kdesilva](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.process.st/kdesilva/32/398_2.png) [@kdesilva](https://community.process.st/u/kdesilva)\
**Post date:** [September 10, 2025, 7:42pm UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/5 "2025-09-10T19:42:18Z")

</div>

@Ellie any word on this? The comma doesn’t work with Data Set Linked Dropdowns or single select dropdowns (though I could have sworn it did at one point).

I ended up having to put placeholder options in the Data Set which isn’t great when a field is supposed to be required.

---

<div class="post-metadata">

**Author:** ![emilyjackson](https://avatars.discourse-cdn.com/v4/letter/e/3be4f8/32.png) [@emilyjackson](https://community.process.st/u/emilyjackson)\
**Post date:** [November 18, 2026, 8:54pm UTC](https://community.process.st/t/any-way-to-clear-a-dropdown-field-using-api-or-the-power-automate-update-fields-action/902/6 "2026-11-18T20:54:25Z")

</div>

On the single-select and data-set-linked cases, the API is probably still validating the submitted value against the configured option list, so null or empty values have no valid match—the comma trick may only apply to multi-choice fields. Until the bug is fixed, if the field must remain required, a placeholder option is the practical workaround; otherwise temporarily make it optional and clear it in a form or UI step before the API call. Worth adding this narrower case to the existing bug report so it isn’t closed as fixed for basic dropdowns.
