You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a custom field for "allergies" or "special medical info", people love to fill in "none", "n/a" etc - even if you ask them to leave it blank in such cases. Then when you run a report showing "people who have the allergies field filled in" there's lots of noise amidst the data.
Makes me think it would be good to have a way to either standardise or filter out such values.
Option 1: Turn it into a selection field, with options "none" or "other". Then we'd need a way to filter in reports "that have [allergies] not equal to [none]"
Option 2: Keep it as a text field, have a convention of putting "-" for people with no allergies. Then we'd need a report to be able to filter "that have [allergies] filled in with a value NOT equal to [-]"
Maybe there are better ways. I've noticed in TryBooking you can wrap a "yes/no" around a text question for scenarios like this.
The text was updated successfully, but these errors were encountered:
For a custom field for "allergies" or "special medical info", people love to fill in "none", "n/a" etc - even if you ask them to leave it blank in such cases. Then when you run a report showing "people who have the allergies field filled in" there's lots of noise amidst the data.
Makes me think it would be good to have a way to either standardise or filter out such values.
Option 1: Turn it into a selection field, with options "none" or "other". Then we'd need a way to filter in reports "that have [allergies] not equal to [none]"
Option 2: Keep it as a text field, have a convention of putting "-" for people with no allergies. Then we'd need a report to be able to filter "that have [allergies] filled in with a value NOT equal to [-]"
Maybe there are better ways. I've noticed in TryBooking you can wrap a "yes/no" around a text question for scenarios like this.
The text was updated successfully, but these errors were encountered: