Why does a multiple choice field with log entries enabled not retain it's value when record is edited?

  • 0
  • 1
  • Question
  • Updated 5 months ago
  • Answered
I'm confused about the behavior of multiple choice fields when log entries are enabled and the field is required.

When I begin editing a record that includes this type of multiple choice field, it loses it's current value when entering edit mode. So if the user edits the record with the intention of making some other change, they are then told when saving that they failed to enter a value in the multiple choice field.

This does not make any sense to me. Is there a workaround?

Also, it seems very broken that reports and filters automatically include the log entries. Also, basing formulas on such a field will break unless a shadow field is created that parses out the real value (i.e. excluding the history).
Photo of Daniel

Daniel

  • 178 Points 100 badge 2x thumb

Posted 5 months ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,436 Points 50k badge 2x thumb
If you still want to use that field type, you can use a form rule to only make it required if the field is blank. I be ie I’ve that should make it non required after its first entry,

Let Ken know if you need help with the Formulas to parse our the elements of the most recent update.

An alternative is to use an Action to log changes, either to a child table or to a field set to log changes.