You are viewing limited content. For full access, please sign in.

Question

Question

If I use pagination can I utilize a variable from an earlier "page" in a latter part of the form?

asked on March 20, 2024

As the title says, I've inherited a massive, six-section form, and I've been receiving complaints that a feature in one of the latter pieces isn't indicating a choice made in the first section of the form. It was my understanding that you cannot utilize a variable from the same form, but it was set up this way once upon a time, and I have to assume it worked once upon a time. 

0 0

Replies

replied on March 20, 2024

Pages in the form are basically just sections - they don’t prevent behavior from one page impacting something on another page.

If you are trying to do something like set the variable from field A as the default value for field B, then you are correct that within the same task/form it won’t work - because default values are populated at the time the form is loaded.  That’s the case in any form regardless of pagination.  And that isn’t something that has changed, it has always been the case.

But if you are trying to use the value in field A as part of a formula in field B, or as part of a field rule that impacts field B, or as a trigger for a lookup that populates field B, then any of those options will work.

1 0
replied on March 21, 2024

To expand on Matthew's answer, you can use Field A in the calculation of Field B. Any changes of Field A will impact Field B immediately; however, you can still manually set Field B after it's been changed.

You can also use Field B as a Lookup or Rule:

Validate Rules available in 11u4+ (and likely Cloud?).

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.