When mapping values to form fields using nested JS object property name-value pairs, whenever I decide to change views (map form field values associated with another upper level JS object/property) and then return to the former view, for whatever reason the form field values revert to their prior values despite the fact that the property values in the JS object were updated/overwritten as intended. Interestingly, if I were to create a button to invoke a script to once again map corresponding JS object property values to their associated form field values thereby overwriting the form field values, problem solved. IMO, this makes no sense whatsoever given the validation script used to map form fields fires whenever a selection provided by the combo box changes and works flawlessly to populate the form fields. However, once again, when any of the form field values are changed and written to their associated JS object property values, changing the selection in a combo box that serves to map form field values to accommodate a new selection and then returning to the previous selection/view, serves to revert the form fields to their prior values as opposed to the values stored in their associated JS object property values. Surprisingly, I do not experience this behavior using a nested JS object with one less level. All considered, what might this behavior be attributed to? Are there certain matters to be taken into consideration when using a nested JS object of more than one level for mapping values to form fields as I am presently doing? Thank you ahead of time.
1
Reply
AdChoices