I think I understand. Thank you!
I've modified my code, and it seems to be working so far. Thank you again. I assume this event always triggers and that the unload event could possibly be avoided somehow (perhaps by someone closing their browser instead of leaving the page first?). Is that correct? I'm just curious and would like to understand more.
Got it! I will try this out and see how it goes. Thank you so much!!! :)
Thank you, SurajK. Is this looking about right? I have multiple lists--do I need to refer to them in each .setEmbeddedData? Sorry for so many questions!Qualtrics.SurveyEngine.addOnPageSubmit(function(type){ //This is the list of approver emails var list = { 1: "example value 1", 2: "example value 2", }; if(type == "next") { Qualtrics.SurveyEngine.setEmbeddedData("ApproverEmail",jQuery("#"+this.questionId).find("select").val()); } //This is the list of approver names var list2 = { 1: "example value 1", 2: "example value 2", }; if(type == "next") { Qualtrics.SurveyEngine.setEmbeddedData("ApproverName",jQuery("#"+this.questionId).find("select").val()); } //etc.});
It's quite long. There's 147 options in the drop-down and as many in three of the variable lists that are setting three different embedded fields. Then there's two other embedded fields that are set only for a few of the options selected.The idea was, instead of having and maintaining 147 different email trigger actions, we would set some of the info for the email in this JS and switch to one email trigger action. Mostly it works... but not these seemingly random times.
Yes, that's right. Force Response is set for that question. I can see a selection was made in the data, but the embedded values were not set by the JS for some reason on a few responses.
I've noticed today that while you could add in piped text and multiple emails in the Reply-to field for an email trigger, you can only enter one email for the reply-to in a task.
That seems to be the case.
I don't think it is just your organization as this happened for me as well... partial links all of the sudden that would not work. Pre-pending the first part of the URL fixed the issue.I did notice that when you make a trigger under Actions and include piped text for the URL (without adding the prepended bit), the URL seems to work fine. I agree that it would be nice not to have surprises like this.
Already have an account? Login
Enter your 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.
