Update Piped Text used as Default Choice after back button | Experience Community
Skip to main content

Update Piped Text used as Default Choice after back button

  • April 23, 2021
  • 1 reply
  • 71 views
S
Forum|alt.badge.img+3

Hi all,
Self-proclaimed jscript noob here, so hoping you can help me out. I'm using a Loop and Merge to get responses from a group of students on what classes they want to request. The looped block has two questions. The first question asks for the Department via MC dropdown:
image.pngThen I have a Page Break so that the second question can use the response above as a Default Choice:
image.pngThe Department field on the second question populates with the Selected Choice from the first question. I've made the first field Read Only as well via jscript so they can't change it.
This has been working fine, except I want respondents to be able to use the back button and return to the first question (Department dropdown) if they realize they have changed their minds. If that happens, and they go back to select a different Department, the Default Choice does not change when the progress forward again. For example, If they select Anthropology from the dropdown, click Next, the first field on the second question says Anthropology. They click the Back button, choose Biology, click Next...and the first field on the second question still says Anthropology.
I'm quite certain there is some jscript and/or embedded data solution but I'm stuck. I don't write code, so please feel free to use the "for dummies" answer if you can help me out! Thanks!!

1 reply

BrianF
Forum|alt.badge.img+1
  • BrianF
  • April 25, 2021

Just to clarify, you are setting the question on the seocnd page by using a script in the default choice?
If so, you might need to remove that and move it to the javascript of the question with the onLoad option which then you can update the current field's value with the selected values of the first question, this way each time the page loads with the second question, it loads the selections.
Alternatively, there could be something wrong with your read-only setup that is not allowing the field to update, but this seems unlikely.

    Terms & ConditionsAccessibility statement