customValuesToMap

Currently, this is only used when saving custom values as a text file. This seems a little weird - can't we just use the existing Map??? Using this does have one advantage : if a custom value is in the Map, and the model is edited, and that field is removed (or renamed), then rebuilding the Map eliminates defunct key/value pairs in the .custom file.