No need to write JavaScript, in my opinion. As you cannot use the NPS question type in your questionnaire, you need to build a NPS-like question on your own (Multiple-choice question with 11 scale points (= number of choices), horizontal position, giving values in reverse order etc.). ! You need to remember to recode the values so that 0 represents 10, 1 represents 9 etc. in your survey. ! Before recoding it looks like the following: ! On the (Vocalize) dashboard you can build the reporting normally by using NPS-metric type for the plain NPS number and other widget types for showing percentages of categories or number of responses per scale point etc . BTW, in this case it would also be possible to include an option of "Don't want to answer/Don't know" etc. if you typically use that in your surveys as an response option. At least I have faced some problems with some surveys when there isn't any option to visibly opt out. Naturally you don't need to force a Respondent to answer to
@JennyMiller, first of all, sorry for missing your question totally! In our case, refreshing the source data within Settings > Project Mapper helped.
Hi @bansalpeeyush29 , to my understanding the mapping should be ok. When it comes to the recoding, if I don't use some demographic in a widget, doesn't it matter even if I haven't recoded all the demographics in a similar way for both projects?
Hi @LaurenK , yes I know about the Comparison widget. In my case it doesn't meet my needs. I think this is now related to the situation that I have two different EE survey projects and I want to see the previous survey's result next to the latest survey's result. Attached an example of what I'm looking for. When I'm filtering (e.g. with org hierarchy or any demographic filter), this previous survey's result (May'18) should reflect that filtering. !
I have just started to use Text iQ and found out that a topic list is a survey-specific list. It seems to be possible to export it from a survey project and import it to another survey project. I haven't yet tried out how the import/export would work in case of maintaining a master topic list on one survey project and copying it to other survey projects (are all changes implemented in a right way i.e. new topics added, changed ones changed, and deleted ones deleted?). However, this is time consuming (and error-prone) due to manual steps required when having several survey projects needing to use the same topic list. Hence I'd like to know whether you have any plans to have some kind of global directory for topic lists and a possibility to map a suitable topic list to a survey project. When the topic list in the global directory would be maintained, the changed would be automatically (or maybe with some confirmation step still) be adopted by the survey projects using the topic list). In
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.