Millisecond Forums

Glad you found an alternative, working solution. Re. the original issue: It's still a problem with Qualtrics. Note that, when you provide a link in HTML, there are *two* things you need to consider: (1) The clickable link "text" that's displayed on the page and (2) the actual, underlying URL the link text refers to (which you can review by examining the respective <a href =...> tag in the HTML's source). They are distinct concepts (see http://www.w3schools.com/html/html_links.asp ), and (2) is what matters.So, what likely happened in your case is that Qualtrics was set up to pipe the identifier into the link *text* only (1 above), but *not* into the actual URL / link *target* (2 above).

Thanks for the reply. I checked the URL settings and they were fine, and for some reason if I copied and pasted the URL I specified into a different survey ending option (redirect participants automatically instead of providing them with a link to Inquisit), it works perfectly. So I've found a different solution to the problem, although I can't explain why one works and the other doesn't! 

This must be an issue w/ Qualtrics not forwarding the parameter properly. If you call the launch page directly with the query parameter set to 'TEST14'http://research.millisecond.com/ianrt/1BATCHtestfile.web?Participantcode=TEST14you will find that Inquisit uses and records the given parameter value just fine (nothing is changed to '11111111').Please check the URL settings in Qualtrics. I'm 99% sure you've actually instructed it to redirect to http://research.millisecond.com/ianrt/1BATCHtestfile.web?Participantcode=11111111instead of properly piping the 6-character alphanumerical code to the redirection URL.