The CSV importer/exporter is a powerful feature, but it does not always play well alongside custom fields. Here are a few things I learned.
Colors are lost. There is no way to export the color of custom fields options, or re-import them.
When importing, if a custom field is created, the order of the options is the one given by the file. You canât decide « High » goes at the top.
And the options available in a custom field are the ones having actual values in the file. If there were no tasks with « Medium » priority in the CSV, you wonât have it either when you import again.
You wonât be able to map a custom field to a column when importing if there is the slightest discrepancy in options (e.g. your column has an option the field does not have).
In some cases, yet to be understood by me, the importer wonât allow matching a column to a custom field and will default to a text field.
Anything I missed?
Thanks @LEGGO for helping with this piece.
Copy. My observation is that the current CSV import I utilized today lacks every option mentioned in the 2018 postâas if the feature set was distilled to the minimum.
A powerful feature with some major limitations, with the most important one being that it is LIMITED to 2000 items. There was no way around this for our 2100+ item project.
As it happens, we are happy about this limitation because otherwise we wouldnât have found https://bridge24.com/ as our alternative. It allowed us functionality that we never imagined when we were using the Asana export.
I am new to Asana and will appreciate your help. I created a form in my project, I created custom fields for each question following this Export data from a form only - #2 by Bastien_Siebman and then I tried exporting the project doing this Forms Export. Before I created the custom fields, I was able to export to CSV, the form information was not there, so that is why I started looking on why it could be, and I created the custom fields. After doing that, now the form custom fields and answers from the forms submission are showing at the list section of the project, but when I tried exporting it to CSV, the actual file that is generated and saved in my laptop is an all files file type, not CSV. When opening it using excel, the formatting is not easy to manipulate and it requires work. What can I do to have it exporting in CSV? I am thinking I set up the custom fields incorrectly.
Hey Bastien, I have this issue. I tried to export several CSVs from different projects but when I open it in excel it has a lot of info including the content of the tasks, but not split in columns, instead, it is an endless sequence of lines with data that is not possible to convert with âtext to columnsâ. I was not able to sort this neither find a solution for it here in the forums. Do you know what might be causing it and what should be the path to the solution? Thank you! Best,
Your Excel probably doesnât use the right separator. Check if the file uses coma or semi-colon, and import the file accordingly. Let me know if you need guidance.
Hi Bastien,
I do have the same issue as Stocco does. I am having users fill out an Asana form and connect the inputs to custom fields. This works perfectly fine in Asana itself and I do see all custom fields populated. However, when opening the csv trying to convert with âtext to columnsâ the custom fields remain empty. I have tried all sorts of separators but do not get the result I am looking for. Do you have an idea for what else I could try or any subs-steps Iâm missing?
Many thanks in advance,
Paula
Iâm having the same issues as everyone else. When I export to Excel all of the information is in one column ânotesâ and it is not separated out. And then I have to copy and paste everything into separate columns anyways and itâs a total time suck. I tried the open a blank doc, select text/csv and import and select comma as separator and the info is still in one column under notes. Help, what am I missing? And why is this so hard?