What is the proper way if using field options in this case?

Am trying to use field options with catalogues  on a site. Am confused about what should be the combination of the type of field and the actual field options. I want to create a "list with the list_multi option.
I was unable to create a list. P tried things like 
[this|that}other

and a=this|b=that|c=other

while keeping the Type of field as "A brief line of translatable/Comcode text".
No list shows up when adding a new catalogue entry  What is the proper way of ud=sing the field option here.
 

Hi,

Field options are defined only for a particular field type. If you want a list, the field type has to be that of a list. Only then can you decide what list field options you may want to specify, and what you want the list contents to be.

Thanks for the clarification.

I have chosen
Multiple values From a list
as the field type and inputed
"Shared Hosting|VPN|Cloud Hosting|Dedicated Servers"
in as the field options, but am not getting what I want when adding an entry (see the attached picture).
I had used
Shared Hosting|VPN|Cloud Hosting|Dedicated Servers (this time without quotes), but am having the sane problem.

This needs to go in the Default field, not the Field Options field. For a list the Default value field is what defines the list contents, and the first term is used as the default list setting.

Am able to get things working, thanks.
How do I exempt a particular field from the 'Sort by" feature?
I have a field of type - A paragraph of translatable/coccode text. I don't want this to appear among the Sort by drop down.

Hi,

Currently you have to do that by making the field non-searchable.
I realise that may not be ideal, there's a tracker issue - 0000302: Field sortable option / Choosing which fields are included in search - Composr CMS feature tracker

Hi,
Does this imply that the contents of this field cannot be searched against with compo.sr's search feature?

That's correct.

Chris Graham said

That's correct.

From “Post #3544”, 19th Dec 2017

I wouldn't want that. I think I'll just remove the sort feature from the template.

It might be we can find some better solution in a live chat if you want to attend one.