Recodes/Numbering not "sticking" | XM Community
Skip to main content
Solved

Recodes/Numbering not "sticking"


RachelTHREE
Level 2 ●●
Forum|alt.badge.img+2
Do you ever have issues with row numbering (whether initial or recoding) not "sticking"/being reflected properly in your dataset? Have you found a solve for it?

Best answer by Anonymous

@RachelTHREE and anyone else who has seen this - we're sorry to hear that you are running into this issue with recode values. It definitely does not sound like this is intended functionality. If you are still experiencing this, could you get a video of it and send it to our support team at qualtrics.com/support-center so that they can take a closer look and escalate it as necessary?
View original

10 replies

Forum|alt.badge.img
  • 8 replies
  • December 4, 2017
I see this quite a bit...it seems the numbering/recode values are rarely stable. So much that I normally go back and check the recode values for each question after I've programmed a survey. If I copy a question, I've found that the response recode values don't start with '1' on the copied question. I've often thought it would be great if the actual recode value showed on the main programming screen for each response option when a question is created.

LibertyW
Level 3 ●●●
Forum|alt.badge.img+5
  • Level 3 ●●●
  • 95 replies
  • January 29, 2018
@RachelTHREE - I found that if I already have data in the question, the recode won't apply to it or it has a hard time "sticking" when you click out of the recode screen. For copied questions, if you click on the " Keep Question export tags" it usually pulls over the recode.

2baprogrammer
Level 2 ●●
Forum|alt.badge.img
  • Level 2 ●●
  • 11 replies
  • February 8, 2018
@RachelTHREE This has happened to me as well. Also noticed sometimes when choosing recoded choices for display logic, the display logic window shows different recoded values, in a different order than I set up, even after refreshing. When this happens to me I save and refresh the page. Anyone else notice this?

  • 0 replies
  • Answer
  • February 16, 2018
@RachelTHREE and anyone else who has seen this - we're sorry to hear that you are running into this issue with recode values. It definitely does not sound like this is intended functionality. If you are still experiencing this, could you get a video of it and send it to our support team at qualtrics.com/support-center so that they can take a closer look and escalate it as necessary?

James
Level 1 ●
Forum|alt.badge.img+5
  • Level 1 ●
  • 15 replies
  • February 20, 2018
I've gotten burned by the recode values changing so I always review them before going live. A good feature would be either a "lock" on the coded values i.e. the numbers are locked by position regardless of content changes due to editing. Or, some sort of reset button which would automatically renumber the recode values starting with 1 [similar to the question renumbering tool].

RachelTHREE
Level 2 ●●
Forum|alt.badge.img+2
  • Author
  • Level 2 ●●
  • 80 replies
  • February 22, 2018
> @TylerK said: > @RachelTHREE and anyone else who has seen this - we're sorry to hear that you are running into this issue with recode values. It definitely does not sound like this is intended functionality. > > If you are still experiencing this, could you get a video of it and send it to our support team at qualtrics.com/support-center so that they can take a closer look and escalate it as necessary? Let me talk to our team here and see if our most recent projects are still experiencing it. Thanks!

Liz
Level 2 ●●
Forum|alt.badge.img+8
  • Level 2 ●●
  • 8 replies
  • March 8, 2018
Hi Rachel, I have also experienced this issue with recoding values. I found that if it would not "stick" then I can refresh my account and it will sometimes correct the problem. It does not seem to be a consistent problem, but I can relate to your frustrations. Liz

  • 1 reply
  • March 8, 2018
I also have had this issue. Usually just refreshing the page corrects the issue.

RachelTHREE
Level 2 ●●
Forum|alt.badge.img+2
  • Author
  • Level 2 ●●
  • 80 replies
  • March 15, 2018
Thanks, all! After talking more internally, looks like we aren't seeing this issue as much anymore!

  • 3 replies
  • April 12, 2018
I am having this problem, sporadically

Leave a Reply