# Multiple choice component values should be separated by comma followed by a space bar **URL:** \ **Category:** Feature Requests\ **Created:** [March 26, 2023, 7:01pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713 "2023-03-26T19:01:25Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\ **Post date:** [March 26, 2023, 7:01pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/1 "2023-03-26T19:01:25Z")
It would be nice if values selected in multiple choice component are separated by comma followed by a space bar instead of just comma. Realized it’s a really hectic exercise to do Split text and then Join Text when I was doing this for 15 columns today. ![Choice](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/0/b0029f68cf07e0732457f35c500aedc1a97dc620.png) ---
**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\ **Post date:** [March 26, 2023, 7:03pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/2 "2023-03-26T19:03:26Z")
Why does that make splitting and joining easier? ---
**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\ **Post date:** [March 26, 2023, 7:07pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/3 "2023-03-26T19:07:38Z")
@david Grammatically it’s wrong if there isn’t a space after comma right? I was making a education app today and the client was very particular about this. They had 15 columns that had multiple select options. In order to display the text on fields, I had to do Split text and then Join to make it grammatically correct. ---
**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\ **Post date:** [March 26, 2023, 10:22pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/4 "2023-03-26T22:22:02Z")
Instead of using split and join, why don’t you use a template to change commas to commas plus spaces. ---
**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\ **Post date:** [March 26, 2023, 11:02pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/5 "2023-03-26T23:02:30Z")
Ooh, good point. Didn’t think of that. But still I wish there was a space added after comma automatically when selecting multiple values in choice ---
**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\ **Post date:** [March 26, 2023, 11:36pm UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/6 "2023-03-26T23:36:21Z")
I think it’s pretty good raw data. Separation with commas can facilitate a transformation to something else. I’m not sure what I’m saying, for example: counting the number of characters, making arrays, replacing commas with “-” signs or emoticons without needing to mistake whitespace, splitting into independent words, etc. I know, spaces also count as one character. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [March 27, 2023, 12:13am UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/7 "2023-03-27T00:13:38Z")
If you need a “grammatically correct” output of a choice component entry, then use a template column and replace all the commas with a comma and a space. There can’t be spaces in a choice component output because then it wouldn’t match with the choices themselves as the choices themselves don’t have spaces that precede the value. ---
**Author:** ![Hassan\_Nadeem](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hassan_nadeem/32/72956_2.png) [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)\ **Post date:** [March 27, 2023, 12:27am UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/8 "2023-03-27T00:27:19Z")
Yes I understand that. I was just saying it would have been good to have if it was separated by a comma and space by default. Just my opinion 😊 ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [April 1, 2023, 4:57am UTC](https://community.glideapps.com/t/multiple-choice-component-values-should-be-separated-by-comma-followed-by-a-space-bar/59713/9 "2023-04-01T04:57:53Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.