BUG: Using the lastResponseId param in qualtrics.py results in a 400 - Bad Request.

[csmcallister]

Expected Behavior

When passing the lastResponseId param to the Qualtrics Create Response Export API, you should get get a 200 response and then be able to get your data using a Get request once it's ready. If there are no new responses after the lastResponseId you pass into the request, a file with only column headers should be downloaded when using the subsequent Get Response Export File API call.

Current Behavior

Including the lastResponseId param results in a 400 - Bad Request.

Possible Solution

• Don't include the lastResponseId and always download all responses. This will get costly over time.
• Try using the startDate or endDate params with the request. However, it is possible that the latest startDate/endDate on-file occurred after a that of a future survey response since the endDate and recordedDate, which is a timestamp that the qualtrics server captures internally but doesn't make accessible via the API, will not always be the same because of partial completion settings. This could result in responses being lost.

  Steps to Reproduce

  If you're running everything for the first time, running python qualtrics.py will work fine. Doing so creates a .txt file with the lastResponseId to be used in the next API call. Run python qualtrics.py again and you'll get the 400 - Bad Request.

  Additional Notes

  Emailed qualtrics support on 9/5 to see if they could troubleshoot.

[csmcallister]

A newline was being passed into the lastResponseId param. That was causing the 400 response.