Currently it's possible to have multiple configurations per content model defined within Solr metadata. The default behavior when this occurs is to combine all fields present from all configurations to present one output to the user. An edge case is possible where the user can define multiple configurations for the same content model and repeat a Solr field. When this occurs the values for the field present in the last configuration will be used which can lead to unexpected behavior.
Need to add validation such that when adding a Solr field we ensure that the field isn't present already for the content model in another configuration.