Dynamic value as Default and Calculated Values

Follow

Roland Maynard

March 19, 2015 14:58

The behavior or the dynamic value parameter for an element is not always intuitive to the end user. It might make more sense to the user to have a "default" value and a "calculated" value fields separately. Thus, the element could have an initial value or a value that is calculated based on other elements. Default values would be set when the form is first launched. Calculated values could not be edited (other than by influencing the other elements that the calculations are based).

5

• 

  Tony Ruth March 19, 2015 21:18

  Hi Roland, not sure if you are aware, but using the Read-Only input for calculated fields doesn't allow the user to modify anything in that field directly and would only change when one of the input fields was changed.

  0

  Comment actions Permalink
• 

  Lea Ronne January 24, 2018 18:16

  Hi, I have found some frustrations with this as well. I would like to have a default value on the form load but then once it is changed it stays changed even if you exit and reenter the form. Currently, I am getting around it by basing it off of another field that has to be selected but my concern with this is if they accidently unselect that field then it could set everything back to the default values. example: if(select field == -1) {default value} else {name of field}. I have put in some safety checks so that it is harder for them to mistakenly uncheck something but it is messy and inefficient. Could there be another option that sets the default value separate from the dynamic value and only operates when the form is first generated?

  1

  Comment actions Permalink
• 

  Guy Swartwout January 22, 2021 19:15

  Yes. Agreed. This "Dynamic Value" drives me absolutely crazy. If I set a default constant value such as field="", that value can be overwritten and maintained. That is not dynamic. That is a default. This is usable if we can understand how it behaves.

  If I use a formula, referencing another element on the page, the value changes dynamically. This is a Dynamic Value, but if that value is set deliberately, it can override the formula. This is incorrect, but it can be avoided by making the field readonly.

  The real problem is when a formula references values from a parent page. This never recalculates dynamically, and that's a BIG, BIG problem for us.

  0

  Comment actions Permalink

Please sign in to leave a comment.