Appears to be fine now. The report I got back on my ticket was that it was an authentication issue.
It’s under past issues now on the status page. (https://status.qualtrics.com/) Hopefully we’ll get some more information on what happened.
@TomG @nistor.adrian Are you on XM Directory Lite or XM Directory Full? Support has suggested that might be the cause. Doesn’t explain why it just stopped working midday yesterday... XM Directory Full. I had the same experience as you...was working fine then all of a sudden yesterday evening it stopped working. Thank you, that is helpful info.
@TomG @nistor.adrian Are you on XM Directory Lite or XM Directory Full? Support has suggested that might be the cause. Doesn’t explain why it just stopped working midday yesterday...
Thanks, we have a ticket open. I’ll let you know if we find out more.
To be clear, I’m just posting the generic call up there for identification. We have the relevant fields filled in.
I’ve been successful filtering in the definition, but not the with the sample call. Results are the same regardless of the sample call filter…For my current needs I only need to get one to work, so I’ll probably set it aside for now.
One follow up question - is it just me or does the filter in the second call, Create Sample, have no effect on the sample? I essentially get 100% of what’s in the sample definition, no matter what.
Thank you, that was very helpful. I was using both in the proper way, maybe something was off with my criteria that led to zero contacts in the sample. I was thrown too by having criteria required in both places. (I understand how that is useful, just that in this case, I only needed one filter.) The way the API generated sample displays in the GUI is a little odd as well. It implies that there are criteria, and that you can remove them. But you can’t see what they are. ¯\_(ツ)_/¯
I will verify that it’s not just you. The search API was a very important part of our processes (we have authenticator lists with up to 500,000 contacts, it’s absurd to have to download all of them) and it just stopped working early this year. Support said it’s because we are on XM Directory Lite, but also tried to claim it’s always been that way and nothing has been changed. Which is obviously complete BS. FWIW I’ve been experimenting with using samples for this purpose - you can download contacts from a sample via API, but I haven’t been able to get the API to generate the new samples successfully.
Sorry, I was trying to refer generally to the ones in documentation under Contacts->Directory Contacts.The change that has blown up our code is to the Search Directory Contacts, which sometime in the last couple months has been restricted from XM Directory Lite.api.qualtrics.com/c79e78a949572-search-directory-contacts List Directory Contacts and List Opted Out Directory Contacts also seem to be restricted, but we don’t use those. There may be others.
@tspr85281@ScottG I did raise this with tech support. It’s apparently a not yet documented feature of simple layout when autoadvance is turned on:“The message that is displayed between the last question and the End of Survey is because the layout is set to simple and auto-advance is enabled, so this message will be automatically included.”“You can get rid of this message either by turning off auto-advance, or by changing the layout from Simple to any other option. “Not clear if we will be able to modify the message in the future. I thought about trying to use JQuery, but decided against it since they are rolling out features with simple layout at breakneck speed.
@ccosart you can edit the end of survey message block, or even redirect the user to a different url i.e. a website page. Ultimately the respondent needs to land on something after pressing submit. If it’s a message your seeing prior to submit button, that isn’t automatic unless it’s already in a template your perhaps using. Any message remains editable, as well as editing the text of the next/submit button. Refer to different options here: Editing the End of the Survey (qualtrics.com) Thanks, but that’s what is hard to figure out - it’s not the end of survey block OR the end of survey message in the Survey Flow. It’s an additional one that is being added in prior to the custom end of survey message.Can’t find a place to edit it anywhere, so I’m guessing it has something to do with the conversion to Simple Layout.
Thank you!I assumed it was something proactively disabling it. Glad this worked. Chris
https://community.qualtrics.com/XMcommunity/discussion/comment/54523#Comment_54523The answer I received from tech support on this:"The skip tokens are not time sensitive and do not have an expiration. The skip token will start in the same place as it previously did unless there were contacts added, which might change some of the order at the end (this was tested on a relatively small list size of 100). "Unfortunately for us, the caveat about unless contacts were added is a big issue, but may not be for your use case.Chris
Again answering my own question after talking to Qualtrics Support. Basically, no you can't do bulk updates in this way with XM Directory Lite. Which, frankly, sucks. A huge step backward in functionality vs Research Contacts.
After talking with Qualtrics Tech Support, I've determined that the XM Directory API won't be able to replicate our process. For many situations, it will, but in the case of an incremental download of a huge contact list, it won't. We are coming up with a new internal process.The key differences were 1) the move to a qualtrics generated string instead of the last recipientID for the skipToken and 2) the order is no longer always the same. Mostly the same, but that's not good enough for the process we are trying to program.
Qualtrics support has confirmed that the migration WILL break the authenticator and recommended closing the survey before migration and reopening it. No word yet on the API issue, but it's hard to imagine that won't be the same.
https://community.qualtrics.com/XMcommunity/discussion/comment/52275#Comment_52275This is very concerning - we definitely have a couple key processes that rely on that functionality.We also have at least one survey that may be ongoing during the migration which uses a contact list for the authenticator and pulls in info from a different contact list via API. I'm not at all confident the migration won't break that process.
Bumping this, but also have a follow up - can the "question requires a response" message be modified on an authenticator?
https://www.qualtrics.com/community/discussion/comment/32988#Comment_32988I thought that might be the case. Fairly new to Qualtrics and it's sometimes surprising the seemingly basic tasks that are challenging/impossible. Though overall it has been a life saver!
Hi, It's definitely a big survey! :-)There would only be one subset per respondent. Along the lines of respondents from Organization A get additional item set A at the end. People from Org B get item set B, and so on, but with 50 -100 different item sets across as many as 300 organizations. ThanksChris
Answering my own question again: A helpful chat with Qualtrics support confirmed that this feature is not supposed to work on Matrix questions and multiple question pages for the same reason it doesn't on mark all that apply questions.
Answering my own question, but the solution I eventually used was including a URL parameter and using that (contact_id) to call the Get Contact API. Then used the retrieved data as piped text in the authenticator message. That way, I was able to look up the meta info from one contact list and use a different contact list for the authenticator.Seems a little contrived, but it is working. Would still be open to other solutions if any one has one, since this will come up on the vast majority of our surveys.Thanks.
I'm trying to avoid custom code if at all possible...
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.
