Asana Custom Fields with enum values in one dataset
Hey together,
I want to setup a zap to create an airtable record based on a created asana task.
Here the dataflow.
As I do not want to create an empty row in airtable in regards of the instant trigger I added a delay of 2min that I was able to fill out the asana tasks and said in step 3 find task by ID. In step 4 i wanted to add the data from step 3 but the two drop downs values from my asana task are standing in the same data record (Custom Fields Enum Value Name “Value1, Value2”. In the data of step 1 they are split as separate data records as it should be in my opinion. But If I use them they are empty cause they are empty when the first trigger is shot cause after I entered the task name and want to fill out the rest of the tasks fields.
Any Idea?
Cheers
Page 1 / 1
Hey there @CarstenM, welcome to the Community!
Hmm, could it be that Asana isn’t able to see the updated details in the custom fields yet? If you test step 3 of the Zap again now is it able to find the values that were added?
If so, you might need to increase the delay time in order to give Asana more time to update things on their end.
Hopefully that’ll do the trick here. Please keep us in the loop on how that goes!
Hey @SamB :-)
The Values are in but when i try to select them i got those double pairs… see below...
Hey there, @CarstenM! Ah, I see - thanks for sharing that screenshot!
It looks like you're running into a know bug with the Find Task by ID Asana search where multiple custom values return as an array. I've added you as an affected user to the bug report! While I don't have an ETA on a fix, this is the best way to stay informed as it ensures you'll be emailed at that time!
We'll also be sure to keep this thread updated with any news. Sorry to not have better news but we appreciate you raising this in community!
That being said I wonder, if we can use Formatter by Zapier (it would in between the current 3rd and 4th steps) to split these items into individual values? So it might look like this:
Hi all, was there a solution to this made as we are having the same issue when setting up one of ours, thanks!
Hi @crreed,
Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the data you’re seeing in Asana so that I can take a closer look at this issue.
Thanks!
Hello @ken.a thanks! Please see screenshots below. I have included the asana task (with custom fields) and the screenshot of Zapier where the custom fields are not individually addressable but rather showing up as an array
Hi @crreed,
Thanks for the screenshots.
I did some digging into this, and it seems like this is a known bug with the Asana integration. Our team is aware of the issue and is working on a fix. I've added your email address as another affected member. That does a few things:
Bring this to the attention of the integration developers
Help track and prioritize fixes
Allows us to notify you via email if/when this is fixed
Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.
In the meantime, we have a workaround regarding this issue here:
Thanks @ken.a; it seems this has been an issue for almost a year (seeing the above thread) and was wondering if there is any additional clarity on the prioritization of fixing this issue?
Hi @crreed,
I understand how frustrating it can be to experience issues without a clear resolution timeline. Unfortunately, due to the constantly changing nature of over 5,000 different integrations on Zapier, it's challenging to provide an accurate ETA for the fix.
There are many variables at play, some of which are completely beyond our control, such as reliance on partners for changes. Please know that we have logged the bug and are working diligently to resolve it as quickly as possible.
We will keep you updated every step of the way. In the meantime, I want to assure you that I am actively advocating for the impact of these issues to be clearly understood.
I know that this doesn't change the fact that you're still waiting on fixes, but please rest assured that we are doing everything we can to address these issues promptly and effectively.
If there's anything else I can do to support you through this, please don't hesitate to let me know.
Hi folks, just wanted to let you all know we just fixed this in the latest version, for the New Task, Updated Task, and Tag added to Task triggers.
There is now a `custom_fields_by_id` field in addition to the old `custom_fields` field. The new one has a list of IDs that correspond to the `gid` provided by Asana, and under each ID is the full custom field object, which contains the text of the field (the field’s name) and the value (what it is set to for that task). This should make these individually mappable on a consistent basis in later steps.
