Hi!
So, when listing a project’s tasks, or GET a specific task, we see that a task payload always includes the values for the task’s custom fields.
For any “multi_enum” custom field, the “enum_value” attribute seems to be is missing.
Any suggested workarounds until this is fixed would be highly appreciated 
Best
Hi @Ran_Oren and welcome to the forum,
Per the documentation, the property you’re looking for is multi_enum_values .
Thanks for this, Phil.
The docs you referred me to are for CREATING a custom field. I’m interested in retrieving the SELECTED VALUES for a field on a specific task.
See my example below where when I query a task, all other types for fields are showing the values, yet for the multi_enum - “multi_enum_values” is missing, along with any other attribute that points on the selected values. All I get are the available values, but there’s no indication what was actually selected for this task.
Thanks,
Ran
Hi @Ran_Oren,
What tool are you using to query/display the task properties? Whatever tool it is, it looks like it hasn’t been programmed to display the multi_enum_values property.
Using the Asana API Explorer to display a task’s custom fields in its native JSON that the API returns, we can see that property:
{
"gid": "1202241953594442",
"enabled": true,
"enum_options": [
{
"gid": "1202241953594443",
"color": "green",
"enabled": true,
"name": "Option 1",
"resource_type": "enum_option"
},
{
"gid": "1202241953594448",
"color": "red",
"enabled": true,
"name": "Option 2",
"resource_type": "enum_option"
}
],
"multi_enum_values": [
{
"gid": "1202241953594443",
"color": "green",
"enabled": true,
"name": "Option 1",
"resource_type": "enum_option"
},
{
"gid": "1202241953594448",
"color": "red",
"enabled": true,
"name": "Option 2",
"resource_type": "enum_option"
}
],
"name": "Test Multi-enum",
"created_by": {
"gid": "159277432863662",
"name": "Phil Seeman",
"resource_type": "user"
},
"display_value": "Option 1, Option 2",
"resource_subtype": "multi_enum",
"resource_type": "custom_field",
"type": "multi_enum"
}
In the above example, I created a multi-enum field with two possible values, Option 1 and Option 2, and for this particular task, I selected them both. You can see they’re both listed under multi_enum_values.
Thanks @Phil_Seeman, I see you are right on this!
This never happened before, very strange that the client behaves this way.
Appreciate your help!
Hey @Phil_Seeman,
Thanks for your posts!
I’m not sure if I should post this in its own thread…
I’m actually having a similar problem in a different library: I can’t find multi_enum_values while using the Java Asana library.
What the problem looks like on my debugger:
Like the OP, I see that the CustomField I’m working with is of type multi_enum, but I don’t see a field within that object that stores multi_enum_values. I don’t see any (Java) fields that could store these values in CustomField.class & wasn’t able to find multi_enum_values in the library.
On the API Explorer end, I do see multi_enum_values listed in the native JSON, as expected. This is when I look up the task that custom field belongs in with the call GET /task/54321?opt_fields=....
So, back in the Java client, I thought those values may be stored in the Task object that CustomField belongs in, but couldn’t find anything there either:
What am I missing here? Any assistance would be super appreciated. Thanks in advance
Hi @anon18524319,
I’m not familiar with the Java library but it sure looks like it hasn’t been updated to handle multi_enum custom fields.
@AndrewWong @sasha_f Any input/info on this?
