Is there a good way to handle checkboxes (select multiple) in reporting?

[Susie Hoskins - Wells Fargo Susie Hoskins - Wells Fargo]

Is there a good way to handle checkboxes (select multiple) in reporting?

We want to put some select-multiple fields in our form, but once this data gets to the data mart, the values are all strung together in one field, with just an intervening blank.  Is there any wisdom on how to use this kind of field in reports? 

[David Munk David Munk]

I would address this at the service design level. Make the values separate fields in the dictionary with a radio button selecting yes or no.  Do this instead of a multi select filed. This way you have the ability to report on these values as they are separate fields.   

[James Fuller]

Hi Susie,

I believe the separation between the data in the string is a "tab" delimiter for multi-select fields in the database.  Therefore, in your report you could use a regular expression to separate the values into an array and loop through them to determine which options were used for that particular field.

[Leslie Tierstein]

As David suggests, this needs to be addressed at the service design level. Multi-select fields are problematic both for reporting and for ServiceLink. However, the display, especially in a horizontally oriented checklist, provides a very nice UI. If you want to keep the UI, you can essentially duplicate the checkboxes as a set of separate fields (as above), but keep these hidden in the service design and populate them via ISF. You could then easily use these fields for reporting purposes.