We need to synchronize the survey responses with our own systems to both and store new response data and to automatically generate detailed reports for the customer from our environment.
We have looked in to a number of avenues but the filtering is limited. For instance, we can’t seem to filter based on session ID.
It seems the best approach would be to use the response ID since it is incremental, but we can’t filter on that as well. We could, however, potentially use pagination to get to the latest responses, but ONLY if the API GET response is guaranteed to be in response ID order. The documentation does not make any statements on this. Are the GET responses always in respond ID order?
If that is not the case, we can use time based synchronization, but this can often be problematic.
Is there another way we are not seeing to accomplish this?
One of our Community Moderators alerted our SurveyGizmo Team of your post. I hope I can provide some options for you.
The Get List call (described below) does return response IDs in order starting with ID 1 and ending with the most recently created ID:
All filters (including those compatible with the response object) are listed here:
You are correct in that you cannot filter directly based on session ID or response ID, though there may be a way for you to work around this.
The session ID can be captured as part of your survey response via a merge code populated into a field on your survey:
If you capture the session id as part of the survey response, it can then be available for filtering (as it becomes an answer to a field/question on your survey). Filtering on a session id captured in a question would look something like this:
I hope this helps! Please feel free to reach out to SurveyGizmo directly at firstname.lastname@example.org should you have further questions!
David – SurveyGizmo
Ok, so the session ID approach you mentioned will work and we already have the merge code populated in our test survey. If we get higher volume of response, it may be good to switch to just looking for new response IDs, so in that case, we can definitely count on the response always ordering 1 to N?
If so, we can just use pagination to get to the latest responses.