Although project documents are not part of the search pages but if a Mica user cusrtomizes the Project schema, there is no way of deciding wether a field is a keyword or not. Fields that are used in sorting query results must be of type keyword (old analyzed).
Current use-case is for CanCOLD where their Project schema has several new fields and the listing is sorted on a custom field which by default is a string. To remedy this, administrator needs to manually change the mapping and reindex all projects. This solution however is temporary since a Index All will destroy the index and the default mapping will once more break the sorting.
Although project documents are not part of the search pages but if a Mica user cusrtomizes the Project schema, there is no way of deciding wether a field is a keyword or not. Fields that are used in sorting query results must be of type keyword (old analyzed).
Current use-case is for CanCOLD where their Project schema has several new fields and the listing is sorted on a custom field which by default is a
string. To remedy this, administrator needs to manually change the mapping and reindex all projects. This solution however is temporary since a Index All will destroy the index and the default mapping will once more break the sorting.A usedful feature to preceed/follow: #3219