Question

Custom HTML field value not getting into repository properly (for Paginated form)

Forms

Updated May 5, 2015

asked on May 4, 2015

We have Custom HTML fields in the form where the verbiage is controlled by the state selected.

For example- if users selected ‘CA’, the verbiage will say- “Please click on the link to access the CA Provider Service Agreement”. If they select something else, it will say that state name.

But in the repository, we are not able to get the same functionality (because we have two forms due to pagination). It shows the ‘static’ value that we have in the form.

Please see some screenshots of the issue.

Fields changing in the front end form.jpg

fields keeping static value in the repository.jpg

State Selected.jpg (26.13 KB)

| Download

Fields changing in the front end form.jpg (147.53 KB)

| Download

fields keeping static value in the repository.jpg (87.68 KB)

| Download

0 0

Replies

replied on May 5, 2015 • Show version history

Hi there,

Does the value show up correctly in View Submission?

CustomHTML value is not a field value, so it's not submitted with form submission. You need to make sure the script running when fill in the form (which may trigger by the field change) still achieve the same behavior when load the submitted form (no field change), you can validate that through View Submission.

0 0

replied on May 5, 2015

Hi,

The value does NOT show up in the View Submission.

What changes can we make to have it show up in the submitted form?

Thanks.

0 0

replied on May 5, 2015

Does your javascript rely on the field change event? you can add an alternative to make it run on forms load.

0 0

You are not allowed to follow up in this post.

Question

Question

Custom HTML field value not getting into repository properly (for Paginated form)

Replies

Sign in to reply to this post.