apologies if this has already been asked, but looking for some guidance on when to import survey data as a field vs content. finding that uploading single and multi select data as content generate the automatic insight graph (which is great) but it doesn't show up in the table view of data to allow me to filter on it at all
Hi Rachael Forster! Currently, we would advise you import data as a field when it is metadata, that you primarily want to use to filter, rather than analyse. Importing as content is when you want to analyse the results (see charts, or even highlight free text). We do not currently allow filtering via content, although this kind of question based filtering is on our radar. (eg. if Question 1 asks for user role, allowing you to filter Question 2 to only responses from a single role from Question 1.) Would love to hear a bit more about your use case and understand what you are trying to achieve?
there are many use cases for bringing something in that you want to both 1) filter on in the table and 2) have the auto-generated insight create a chart for. for example, I recently did a survey where I had multiple single and multi-select questions that I wanted to have the auto insight create a chart for when I presented out to my stakeholders. however, I also wanted to be able to filter it in the table as analyzing so I could look at different data segments. for example, I want to see all the responses where someone selected "satisfied" and "very satisfied as an answer" what kind of roles were they in, what kind of orgs did they work at, etc. I actually can't think of a use case where I wouldn't want to bring something in as both content with auto-insight/chart generation and filterability
Makes total sense Rachael Forster! Thanks for the detailed response. This kind of filtering is definitely on our radar to improve - getting input from customers like yourself helps us prioritise appropriately so thank you!