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

Question

Question

How do you prevent a lookup/calculation from rerunning in later User Tasks?

asked on May 8

I have a field on the submission form that is initially populated by a lookup/calculation based on other field values. However, the user is also allowed to manually adjust that calculated value afterward if needed.

The issue is that when the form moves to a later User Task, the lookup reruns when the form loads, which recalculates the field and overwrites the user’s manual changes.

What’s the best practice to prevent the lookup/calculation from rerunning in future User Tasks so the user’s updated value stays intact?

I’d rather avoid using JavaScript to capture the original value on load and then restore it again after the lookup completes.

0 0

Replies

replied on May 11

The suggestion from Luis is a good answer. Another approach would be to have a second copy of your form without the lookups that you could use at later steps. Depending on the number of fields and the overall complexity, I might go that route just to keep things simple.

3 0
replied on May 12

I like this one! wink

0 0
replied on May 8

Hi Jeffrey, 

You could use a formula-based approach by having the lookup populate a hidden source field, then using a conditional formula to populate the final field only when that final field is still blank.

For example:

=IF(Final_Value="", Lookup_Value, Final_Value)

Conceptually, this means: if the final editable value has not been set yet, use the lookup value; otherwise, keep the value that was already entered or adjusted by the user. This helps prevent the lookup/calculation from overwriting manual changes in later User Tasks.

Try it and let me know. 

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

Sign in to reply to this post.