Dear QRTE users,
As some of you have tried, and reported back to us, v15 of the QRTEngine seems to run fine on the new Qualtrics JFE engine. However, embedded data wasn’t stored when using this version. This issue has now been taken care of, and we suggest everyone to switch from v16/v17_jfe_fix to v15_jfe_fix. The js file can be found here:
Please let us know if there are any other issues with this version and look for notices on this website as we try and get the latest version of the QRTEngine, v16, working again in Qualtrics.
Thanks again for your understanding!
Dear QRTE users,
As you may have noticed, fixing the QRTEngine has taken longer than originally planned, due to complexities involved in the recent the Qualtrics update.
There seem to be a myriad of different problems, and it’s hard to keep track of individual cases through comments/forums/posts. Therefore, we suggest any issues with the current version of the QRTEngine to be posted to our issue tracker on github, https://github.com/ErwinHaasnoot/QRTEngine/issues. Make sure to include a description of the problem in the post and a link to related exported surveys (.qsf files). Or if uploading the .qsf is not an option, you can share the survey with me at ehaasnoot1[at]sheffield.ac.uk (make sure to mention the name of the survey in the issue you’ve created). Please note, this is the e-mail my Qualtrics account is registered to, I no longer have access to the mailbox.
The same goes for issues with the parser. It’s possible that due to recent updates in the Qualtrics Survey Engine, the file output structures changed, which would affect the parser as well.
I’m hoping to spend more time tonight, tomorrow night and over the weekend to tackle these issues, so hopefully we can get a broad range of issues in the tracker, which would allow me to test possible fixes as thoroughly as possible.
We are very sorry for any inconvenience caused by this and would like to thank you for your understanding.