Choose Unique And Multi-value Wisely When Adding Option List as property to a Schema

When building all the schema you will determine the properties as best you can but will want to add or change schema later.  In some cases that is cool but in other cases changing the schema can be a challenge.  One such time is when working with option list properties. In the screenshot below I have highlighted 2 properties: Unique and Multi-value. Once you set these values and save them you cannot edit them.

This is new member

Note that after save we go to edit and see this. Note you cannot edit.  This is by design because as a developer you know the implications of changing these once you have data in these fields.

So be careful when choosing the options. Now there is a way to fix it afterwards but not a nice one  The way to fix it is to create a new property with the proper settings then use script to migrate the data to the new property, flagging any with possible issues for manual fixing later. 

If you have more of these please let us know and we can add them.