# Updating custom field values (dropdowns) **URL:** \ **Category:** API & Developers\ **Created:** [14 December 2022 22:55 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357 "2022-12-14T22:55:40Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Darren\_Loureiro](https://luna1.co/8d76cd.png) [@Darren\_Loureiro](https://forum.asana.com/u/Darren_Loureiro)\ **Post date:** [14 December 2022 22:55 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/1 "2022-12-14T22:55:40Z")
I am attempting to update via API a custom field value on a Project but am receiving the error message “Custom field with ID 1201830799946826 is not on given object”. I created the Project and successfully associated the custom field gid 1201830799946826 to the Project via POST. When I attempt to PUT to [https://app.asana.com/api/1.0/projects/1203547940638522/](https://app.asana.com/api/1.0/projects/1203547940638522/) with the JSON below, I receive the error message. What is the correct JSON syntax to update the custom field value on a Project? { “data”: { “custom\_fields”: { “1201830799946826”: “1201830799946827” } } } ---
**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\ **Post date:** [15 December 2022 01:13 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/2 "2022-12-15T01:13:33Z")
Hi @Darren_Loureiro, I think we need some clarification about what exactly you’re wanting to do. Are you trying to add an additional `enum` option to an existing `enum` type custom field, or something different? ---
**Author:** ![Darren\_Loureiro](https://luna1.co/8d76cd.png) [@Darren\_Loureiro](https://forum.asana.com/u/Darren_Loureiro)\ **Post date:** [15 December 2022 17:06 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/3 "2022-12-15T17:06:00Z")
Hi @Phil_Seeman , thanks for looking into my question. My ultimate goal is on the Project details page, for a Custom Field named Test-Phase, I want the value to be set as test-option-1 as opposed to the other preset options. Test-Phase is a custom field already created in the Workspace with properties “resource\_subtype”: “enum”,“resource\_type”: “custom\_field”,“type”: “enum”. I used POST /projects/{project\_gid}/addCustomFieldSetting and successfully added Test-Phase to custom\_field\_settings and saw that its parent and project are the correct project. I next used PUT /projects/{project\_gid} with the JSON below and received the error previously mentioned, { “data”: { “custom\_fields”: { “1201830799946826”: “1201830799946827” } } } 1201830799946826 is Test-Phase’s gid and 1201830799946827 is a gid of the enum\_option with name test-option-1. With this attempted PUT, my expectation was to update the Project’s JSON API custom\_fields from ““custom\_fields”: ” to below. I believe with the steps taken and API state changed to below, I’ll then have accomplished my ultimate goal. “custom\_fields”: [ { { “gid”: “1201830799946826”, “enabled”: true, “enum\_options”: [ { “gid”: “1201830799946827”, “color”: “yellow”, “enabled”: true, “name”: “test-option-1”, “resource\_type”: “enum\_option” }, { “gid”: “1201830799946828”, “color”: “none”, “enabled”: true, “name”: “test-option-2”, “resource\_type”: “enum\_option” }, ], “enum\_value”: { “gid”: “1201830799946827”, “color”: “none”, “enabled”: true, “name”: “test-option-1”, “resource\_type”: “enum\_option” }, “name”: “Test Phase”, “description”: “”, “created\_by”: { “gid”: “1203460510854392”, “name”: “Jane Smith”, “resource\_type”: “user” }, “display\_value”: “test-option-1”, “resource\_subtype”: “enum”, “resource\_type”: “custom\_field”, “type”: “enum” } }] ---
**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\ **Post date:** [19 December 2022 14:38 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/4 "2022-12-19T14:38:16Z")
@Darren_Loureiro, OK, got it. So before I explain the situation in detail, one initial question: do you have a Business or Enterprise Asana subscription, or just Premium (the differences are relevant for what you’re trying to do)? ---
**Author:** ![Bala\_Koppella](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bala_koppella/32/99098_2.png) [@Bala\_Koppella](https://forum.asana.com/u/Bala_Koppella)\ **Post date:** [19 December 2022 16:53 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/5 "2022-12-19T16:53:51Z")
Hi Phil, Our plan is ‘Enterprise organization’. ---
**Author:** ![Bala\_Koppella](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bala_koppella/32/99098_2.png) [@Bala\_Koppella](https://forum.asana.com/u/Bala_Koppella)\ **Post date:** [19 December 2022 17:38 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/6 "2022-12-19T17:38:49Z")
@Phil_Seeman ---
**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\ **Post date:** [23 December 2022 00:51 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/7 "2022-12-23T00:51:15Z")
Hi @Bala_Koppella, Hopefully you’re from the same organization as @Darren_Loureiro. 🙂 In any case, I think the key point here is that there are two different levels of custom fields. You can set up custom fields at the _ **portfolio** _ level, in which case the values of those fields are set and stored at the _project_ level in projects within that portfolio; and you can set up custom fields at the _ **project** _ level, in which case the values are set and stored in _tasks_ within that project. Having said that, let’s move onto Darren’s use case… > [@Darren\_Loureiro](#): > > My ultimate goal is on the Project details page, for a Custom Field named Test-Phase, I want the value to be set as test-option-1 Since the goal is to affect the custom fields on the _project_ details page, he is referring to a _ **portfolio** _-level custom field. So to do that, add the project to a portfolio, then [add the custom field to that portfolio](https://developers.asana.com/docs/add-a-custom-field-to-a-portfolio). That makes it available to set on all projects in that portfolio. At that point, you should be able to use your `PUT` endpoint to set the value on the custom field in that project. ---
**Author:** ![system](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/system/32/276370_2.png) [@system](https://forum.asana.com/u/system)\ **Post date:** [30 May 2025 19:03 UTC](https://forum.asana.com/t/updating-custom-field-values-dropdowns/281357/8 "2025-05-30T19:03:04Z")
Closed on 30 May 2025 19:03 UTC