Add a new column in Imported data Project

@Sura Sadly, this is a limitation with imported data projects. You are unable to add additional columns. Your best bet is to reupload your data as a new imported data project. 

Once uploaded, map the imported data project to the existing dashboard. AFTER you have mapped the new imported data project, you can remove the initial imported data project from the dashboard. If you do it in this order, you shouldn’t have to rebuild the dashboard. 

Hi @jmborzick , Thanks for replying . But , then for Text IQ fields. i need to do it again right?

@Sura No, you shouldn’t have to. Text IQ is mapped to a field, not a data source. As long as you map the new data source to the same fields as the old one (which is why it’s important to delete the old source after you map the new one) Text IQ should pick up the comments just fine. The only reason you’d need to work on Text IQ again is if the additional column you’re adding has the text. 

Thanks @jmborzick , Just a doubt . It isn’t that we have to add the new Comment (open text ) section for Text iq functionality and update the topics right?

@Sura, no, assuming you map it to the same field, Qualtrics will grab the comments from the new source and analyze them according to the rules you initially established.

You can try creating a custom field, then export your data and add your new data to the new field you just created before re-importing.  I just tried this method and was successful. 

You can also add a column with the API : https://api.qualtrics.com/f1dc5b722f95b-add-columns-to-imported-data-project

Fields created via the custom field editor will appear as EDs in your Data & Analysis tab, fields created with the API will appear as regular fields.

Be sure to have an unique ID or to delete existing records when you reimport your data to avoid  duplication.

Hi @Sura, You can give a try by Export your data in CSV, add a new column with the required values in a spreadsheet and then re-import the data.

Just wanted to add to this a few caveats I’ve found, this is as of 2024 / 2025 (in case Qualtrics engineers decide to change things!):

1. Re the use of the API as per above link is straight forward and allows you to create what ever field type you like which is really powerful - eg. create a copy of an existing field but in open text form that then allows you to push it through TextiQ (for the purpose of creating topics based on some external reference code for example - clever!).  However support documentation is / was unclear about the capitalisation of id when using a webservice task (to update the field).  It's now (end 2024) been confirmed by support that this should be all lower case for an imported project.  You have to know this as the D&A headings which you'd normally refer to show's it differently!

   

2. Field names in the email task workflow…. do not use brackets in the label as it seemed that this can’t be picked up in the email task (if you want to message yourself confirming the task has run).

Hope that helps someone

Thanks

Rod Pestell