from @pgorecki
I hope someone could clarify to me the results I'm getting from the API (this is for user 2bdc52ee-4dea-419e-b582-fa1629686dfd)
I'm looking at submissions of a client b10c742f-0559-4f30-8a64-a232961fd581 (dedupClientId 096a92f0-3779-11e8-985f-02fe61f7863e)
https://api.hslynk.com/survey-api/rest/clientsurveysubmissions/b10c742f-0559-4f30-8a64-a232961fd581
in the response there are 3 submissions. Let's focus on the first one, which is:
submissionId f376152c-491f-48e8-a689-3b3801248045 (for surveyId bd69c748-e8a4-4e62-bab7-f4cb229998af)
I want to know the responses in the submission f376152c-491f-48e8-a689-3b3801248045. I'm using v3 api which requires dedupClientId:
https://api.hslynk.com/survey-api/rest/v3/clients/096a92f0-3779-11e8-985f-02fe61f7863e/surveys/bd69c748-e8a4-4e62-bab7-f4cb229998af/submissions/f376152c-491f-48e8-a689-3b3801248045
the first response in the resulting list is d7a022ee-0cd7-424a-9ed1-37f7dd2a0414
which is for clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 :thinking_face: (dedupClientId 096a92f0-3779-11e8-985f-02fe61f7863e)
clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 does not exists (or at least is not searchable) :thinking_face:
so let's see where if 1a75af4e-5f75-423a-ba39-e69e7db10242 can be found by looking at dedupId
https://api.hslynk.com/hmis-globalapi/rest/clients/096a92f0-3779-11e8-985f-02fe61f7863e
nope, only one client b10c742f-0559-4f30-8a64-a232961fd581 is there :white_frowning_face:
can anybody explain me what's going on in here? why I'm getting responses with clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 instead of b10c742f-0559-4f30-8a64-a232961fd581 ?
from @pgorecki I hope someone could clarify to me the results I'm getting from the API (this is for user 2bdc52ee-4dea-419e-b582-fa1629686dfd) I'm looking at submissions of a client b10c742f-0559-4f30-8a64-a232961fd581 (dedupClientId 096a92f0-3779-11e8-985f-02fe61f7863e) https://api.hslynk.com/survey-api/rest/clientsurveysubmissions/b10c742f-0559-4f30-8a64-a232961fd581 in the response there are 3 submissions. Let's focus on the first one, which is: submissionId f376152c-491f-48e8-a689-3b3801248045 (for surveyId bd69c748-e8a4-4e62-bab7-f4cb229998af) I want to know the responses in the submission f376152c-491f-48e8-a689-3b3801248045. I'm using v3 api which requires dedupClientId: https://api.hslynk.com/survey-api/rest/v3/clients/096a92f0-3779-11e8-985f-02fe61f7863e/surveys/bd69c748-e8a4-4e62-bab7-f4cb229998af/submissions/f376152c-491f-48e8-a689-3b3801248045 the first response in the resulting list is d7a022ee-0cd7-424a-9ed1-37f7dd2a0414 which is for clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 :thinking_face: (dedupClientId 096a92f0-3779-11e8-985f-02fe61f7863e) clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 does not exists (or at least is not searchable) :thinking_face: so let's see where if 1a75af4e-5f75-423a-ba39-e69e7db10242 can be found by looking at dedupId https://api.hslynk.com/hmis-globalapi/rest/clients/096a92f0-3779-11e8-985f-02fe61f7863e nope, only one client b10c742f-0559-4f30-8a64-a232961fd581 is there :white_frowning_face: can anybody explain me what's going on in here? why I'm getting responses with clientId 1a75af4e-5f75-423a-ba39-e69e7db10242 instead of b10c742f-0559-4f30-8a64-a232961fd581 ?