View-only response pages being decommissioned after February 18, 2023 | XM Community

View-only response pages being decommissioned after February 18, 2023

  • 30 January 2023
  • 6 replies
  • 13 views

Userlevel 5
Badge +13

I was just notified that https://qualtrics.com/CP/Report.php?SID={surveyId}&R={responseId} is being decommissioned after February 18, 2023. How can I view a response without having to fire off an event or email trigger? 😥


6 replies

Userlevel 7
Badge +30

Are you just interested in viewing a response yourself? If so, are you able to use the View Response or Export to PDF options in Data & Analysis?
image.png

Userlevel 5
Badge +13

Going through the Qualtrics admin system does not fit with my process flow which heavily uses the https://qualtrics.com/CP/Report.php?SID={surveyId}&R={responseId}. Is there an API equivalent to this? I need a programmatic solution, not a manual one.

Badge

Echoing OP request. MatthewM the request is to have a URL to a specific response. Can you clarify the reason for deprecation/how we can support this use case?

Userlevel 7
Badge +30

https://community.qualtrics.com/XMcommunity/discussion/comment/55568#Comment_55568I'm not a Qualtrics employee so I have no insight on why this feature is being deprecated. Perhaps one of the moderators, Michael_Cooksey , AmaraW or JoseS, can chime in?

Userlevel 7
Badge +20

Hello w.patrick.gale MatthewM m_brown_253, thank you for bringing this topic to our attention! I reached out to our product management team & unfortunately, there is currently no solution available for this use case using the new response report links.
They are currently looking into resolving this issue by making a public API available that users can call in order to retrieve a new response report link. However, there is currently no timeline specified for this proposed solution.
I will make sure to update this thread if I receive any news or updates regarding this public API.

Userlevel 5
Badge +13

It looks like the Report.php script is no more. Sad because there is no API endpoint to replace this functionality.

Leave a Reply