5 Replies Latest reply on Aug 28, 2016 12:44 PM by Sanford Whiteman

    Multiple Selections Option on Form Field Editor

    Tom Kerlin

      Hi all,

      I have a form field where users might need to select multiple values from drop-down box. In the form editor I checked off multiple selections checkbox and another option appeared underneath it titled "Visible Lines" (screenshot is below).

       

       

      1.) Why is Visible Lines an option when Multiple Selections is checked?

      2.) It won't let me select a number less than 4; is this because I have 4 values for field?

       

      Additional Questions:

      3.) Is it considered a best practice to make all values visible for fields where more than one value can be selected?

      4.) How can users tell if it's possible to select more than one value for field? I pointed this out for users on form (see screenshot below). Thoughts?

      5.) I assigned String field type for this field, but should I have assigned Text Area field type instead? I was concerned about max number of characters each field type can successfully collect and store, especially when users can technically select all values.

       

      Thanks

      Tom

        • Re: Multiple Selections Option on Form Field Editor
          Sanford Whiteman
          1.) Why is Visible Lines an option when Multiple Selections is checked?

          Because an HTML multi-<SELECT> always has an option for the size, e.g. visible rows.  This isn't Marketo's concept.

           

          2.) It won't let me select a number less than 4; is this because I have 4 values for field?

          No, it's merely an enforced aesthetic choice, probably so the widget looks like a multiselect. You can actually reduce this below 4 using JS, but I don't know why you would unless you only had 2 options (in which case you should be using some other kind of widget).

           

          3.) Is it considered a best practice to make all values visible for fields where more than one value can be selected?

          I find shift-clicking to include items that are both in and out of view to be a poor UX.  But maybe that's just me.

           

          4.) How can users tell if it's possible to select more than one value for field? I pointed this out for users on form (see screenshot below).

          It's a standard HTML widget, so either they're familiar with it or they're not! I think a briefer "(multiple selections allowed)" is fine if you're using the widget.  But I also don't recommend multiselects when checkboxes will do.  While the advantage of the multi is that it's natively scrollable, you can do the same thing with a long list of checkboxes by putting them in a container.

           

          A 3rd approach to multiselects is a "sticky dropdown" where a container drops down but doesn't go away while the user makes selections. until the user specifically clicks away or clicks some kind of "done" button; the current selections are then reflected in the single visible line as visually distinct items like

           

          5.) I assigned String field type for this field, but should I have assigned Text Area field type instead? I was concerned about max number of characters each field type can successfully collect and store, especially when users can technically select all values.

          I agree that you should use a Text (textarea) field if you would overflow a String with all values.

           

          But you can also rethink whether this should be all one field.  Having multiple boolean fields can be more manageable for Smart Lists. You only need to match on true instead of doing a string contains constraint, for example, and improper string matching can catch you up ("mortgagebot pos+los" matches "mortgagebot pos").

          1 of 1 people found this helpful