Enabling "removed" local custom fields in list view on project.

English Forum Developers & API
1

Hello everyone, I know I’m boring at this point but ehh :slight_smile:

So what happened is that I accidentally “deleted” a custom field from a project, however when I check the tasks the field is still there but grayed out.

I am wondering if there is a way to change the value of this field on the project-wide level (preferably so it’s also back in the list view) to enabled again?

I did not get an undo button and I am not the person that created the field originally.
JSON of the custom field after the change, pulled from a task:

“gid”: “1204067423571884”,
“enabled”: false,
“enum_options”: [
{
“gid”: “1204067423571885”,
“color”: “green”,
“enabled”: true,
“name”: “Yes”,
“resource_type”: “enum_option”
},
{
“gid”: “1204067423571886”,
“color”: “red”,
“enabled”: true,
“name”: “No”,
“resource_type”: “enum_option”
}
],
“enum_value”: {
“gid”: “1204067423571886”,
“color”: “red”,
“enabled”: true,
“name”: “No”,
“resource_type”: “enum_option”
},
“name”: “Welcome Call Complete”,
“description”: “”,
“created_by”: {
“gid”: “1203761628868841”,
“name”: “Redacted”,
“resource_type”: “user”
},
“display_value”: “No”,
“resource_subtype”: “enum”,
“resource_type”: “custom_field”,
“is_formula_field”: false,
“is_value_read_only”: false,
“type”: “enum”
},

When pulling the project I do not see that custom field.
I already reached out to Asana support to see if there is anything that can be done.

My question is am I able to re-upload this field to the list view via API or to enable it on the project level, does anyone have any experience with this?

2

You can just use the custom_field_settings endpoint to add back a custom field setting for this field in that project.

3

@Phil_Seeman thanks for the reply!

I’m afraid that I don’t quite follow you.

When using custom_field_settings in client.projects.get_project I receive this response:

{
“data”: {
“gid”: “1205154296760258”,
“custom_field_settings”: [
{
“gid”: “1205176507759392”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759414”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759419”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759421”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759423”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759425”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759427”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759429”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759433”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759437”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759439”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759443”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759447”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759449”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759453”,
“resource_type”: “custom_field_setting”
},
{
“gid”: “1205176507759455”,
“resource_type”: “custom_field_setting”
},

I first retrieved it to be able to understand how the data is structured before I updated it however I’m a bit confused now.

Do you maybe have a json example of what you were saying?

4

@Phil_Seeman
I managed to take care of this issue.

I found the same custom_field in another project that had the same gid.
I added that to our organization’s field library and that way I was able to readd the field to the project where I removed it.

I am still interested in your suggestion as it will help me understand Asana’s under-the-hood a bit better.

Thanks either way!

5

I ws suggesting to use this endpoint to add the custom field back into the project: Add a custom field to a project

6

When you delete a custom field, all tasks that were using it keep the original value, but it can’t be used any more.

You can create a new custom field with exactly the same name, but it will not be the original. You will see 2 customfields, with the same name, in your edit panel.

The original custom field ID is done for ever, and it’s impossible to get it back.
Also, all values of your enum have different ID, and for them too, if you recreate the “same” custom field, with the same values, their id are different, so they are not really the same.

7

@Phil_Seeman thank you, I missed that on my first pass.
I looked into it a bit deeper and it seems like that would have solved my issue as well :slight_smile:
Thank you very much.

1 Like
8

@Frederic_Malenfant I appreciate your response.

However I was able to re-enable the field.
Please keep in mind that the thread title is "Enabling “removed” local custom fields in list view on project.

I am aware that deleted ones cannot be recovered, however if you remove a field from the project list view the values associated with the custom field still remain on the task, however they are greyed out.

I was able to reenable the custom field as I found the same one in another project we used.
I added it to my organization’s field library and re-added it to the project where I deleted if off from and that did the trick. I have no idea how a local custom field’s gid did not change when they duplicated the project to create the one I was having issues with.

Pasting the json output from one of the tasks in the project where I had the issue as proof that the custom field has been enabled:

{
“gid”: “1204067423571884”,
“enabled”: true,
“enum_options”: [
{
“gid”: “1204067423571885”,
“color”: “green”,
“enabled”: true,
“name”: “Yes”,
“resource_type”: “enum_option”
},
{
“gid”: “1204067423571886”,
“color”: “red”,
“enabled”: true,
“name”: “No”,
“resource_type”: “enum_option”
}
],
“enum_value”: {
“gid”: “1204067423571886”,
“color”: “red”,
“enabled”: true,
“name”: “No”,
“resource_type”: “enum_option”
},
“name”: “Welcome Call Complete”,
“description”: “”,
“created_by”: {
“gid”: “1203761628868841”,
“name”: “Redacted”,
“resource_type”: “user”
},
“display_value”: “No”,
“resource_subtype”: “enum”,
“resource_type”: “custom_field”,
“is_formula_field”: false,
“is_value_read_only”: false,
“type”: “enum”
}

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.