# Aggregations don't work in Kibana after Elastic stack upgrade to 7.2 **URL:** \ **Category:** Kibana\ **Created:** [July 10, 2019, 4:10pm UTC](https://discuss.elastic.co/t/aggregations-dont-work-in-kibana-after-elastic-stack-upgrade-to-7-2/189825 "2019-07-10T16:10:31Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Martin\_O](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@Martin\_O](https://discuss.elastic.co/u/Martin_O)\ **Post date:** [July 11, 2019, 3:47pm UTC](https://discuss.elastic.co/t/aggregations-dont-work-in-kibana-after-elastic-stack-upgrade-to-7-2/189825/4 "2019-07-11T15:47:46Z")
E.g. I tried this, but there are no fields, that end with '.keyword' in my case: > [@Sorting rows in Kibana based on keyword field](https://discuss.elastic.co/t/sorting-rows-in-kibana-based-on-keyword-field/109968/5): > > Hi Marin, This is a confusing topic even to me and I've been working on Kibana for over 2 years. But here's the issue. It's all about the mapping of the field. Strings can be loaded into Elasticsearch as 2 different types text and keyword and they are commonly stored both ways. For example, in filebeat you should have beat.name and it should be sortable; If we go to the Dev Console and do a GET on the filebeat index mapping we see that beat.name is "type": "keyword". The fact t… --- _[View the full topic](https://discuss.elastic.co/t/aggregations-dont-work-in-kibana-after-elastic-stack-upgrade-to-7-2/189825)._