Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fetch_survey does not capture very recent data #124

Closed
vince-p opened this issue Aug 5, 2019 · 2 comments
Closed

fetch_survey does not capture very recent data #124

vince-p opened this issue Aug 5, 2019 · 2 comments

Comments

@vince-p
Copy link

vince-p commented Aug 5, 2019

If I generate some test responses in qualtrics and then immediately try to run fetch_survey, it does not import the new responses. This is the case even with 'force_request = TRUE'.

I found a clue on this page: https://www.qualtrics.com/community/discussion/1888/qualtrics-api-export-missing-latest-results
It suggests that the API can capture very recent data by setting an end_date value.

This also works for fetch_survey BUT it only works if a different end_date is used for each request. I.e., the following is what happens:

  1. If I generate test responses in qualtrics then try fetch_survey, the new responses are not captured.
  2. If I set an end_date value for fetch_survey with a value in the future, the new data is imported.
  3. If then generate more test data in qualtrics and try again to import using fetch_data, it does not capture the new data. This is true even if I use the same end_data value as step Base_url: let user fill out the 'yourdatacenterid' and add to README where this can be found #2.
  4. If I try with a new, different end_data value then the fetch_survey command does work.
@juliasilge
Copy link
Collaborator

Thanks for your patience with this @vince-p!

First off, I would just like to do a little screaming. 🙀What on earth kind of behavior is this; I MEAN REALLY.

OK, so where do we go from here? It seems like this is the API behavior, and not the R package per se. The R package supports the parameters that the API accepts, and it seems like changing those back and forth is how to get those very recent responses, if necessary.

I do have a call with a Qualtrics support person this coming week, and I'll bring this up. I don't believe there is much I can do from the R package side that will fix this, since it is the API behavior. Do you have any different ideas?

(I am feeling thankful that I don't have use cases where I need to see responses immediately right about now.)

@juliasilge
Copy link
Collaborator

We have recently moved to the newest API in #135 which I hope may solve issues like this one. Please open a new issue if you continue to have problems! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants