Auto-binding vs Single Database update for multiple fields

If I have a form with multiple fields of various types, which is preferred in terms of WU? Which will produce lower WU or will it be exactly the same?

  1. Use auto-binding on all fields so they update immediately.
  2. Do not use auto-binding and update all fields with a workflow when the user clicks a “save” button.

For user experience, I prefer auto-binding, but if it will end up creating greater WU, I will use the save button.


did you find any answer here?

Would be interesting to understand what is better from a WU perspective but also from a performance perspective.

any update on this?

I’ve done some testing on this, and I found changing multiple fields with a workflow consumed less unless you are only changing 1 or 2 fields. Each auto-bind will use at least 0.6WU, whereas if you are changing multiple fields in the same Thing, each additional field you are updating on that Thing adds a fractional amount of WU. For example, I have a datatype with about 30 fields. Auto-binding all 30 of these fields would be around 18 WU (0.6WU per field), whereas when I used "Make Changes To A Thing’ and then chose all 30 fields to change, it cost around 3WU for me in this specific example.

1 Like