How can I add a report custom field to a CSV Export?

Hi,
Recently I've created some report-level custom fields to help some extra information. Now I've would like to export the information stored on this custom fields along with the default csv export information.
Unfortunatelly there is no how-to explaining how to add report custom fields to csv exports. Can someone help me with this?
Best Answer
-
Expensify concierge gave me a hand with this. The correct sintax is {field:Bank}. Where Bank is the name of the custom field you created.
Answers
-
-
Yes, I've read that. I know how to create a custom export, but how can I add a field I created to this custom export? I could find anything on that.
-
Thanks for clarifying @aas87 !
Can you try adding {report.customField.Name_of_Report_Field}? You will need to use an underscore for any non-letter (e.g, space) or number in the name of the report field. For example, if your field is named "First Name", you would use {report.customField.First_Name}.
-
Hi, Mark. Thanks for your answer. I tried {report.customField.First_Name} but it didn't work. I get an empty column when exporting.
-
Hey @aas87,
This could be because the user who's report you are exporting does not have their first name field filled within their settings. Could you double check this?
-
Hi, Matt.
In reality I'm using a custom field I have created. The field is filled on the reports. Let me try to give further context. I've created a field where I register the name of the bank where the report submitter has his account. I named that field Bank. Now I would like this info to show on the custom export, but I can't seem to find how to make this work. I've tried {report.customField.Bank} the result is an empty column, even though there is information on the reports.
-
Hm, I believe you were right at the beginning -- it should be {field:Bank}, if this is a Report Field. If that's not working, I think we should switch back to Concierge so that we can take a closer look at the export format and your policy setup.
-
Hi, Jeremy. {field.bank} is working as expected and solved the issue for me.
-
Awesome -- thanks for confirming!