# Can't see all fields when Visualize-\>Aggregation-\>Terms is selected in Kibana **URL:** \ **Category:** Kibana\ **Created:** [March 9, 2017, 3:30pm UTC](https://discuss.elastic.co/t/cant-see-all-fields-when-visualize-aggregation-terms-is-selected-in-kibana/78010 "2017-03-09T15:30:07Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [March 9, 2017, 7:35pm UTC](https://discuss.elastic.co/t/cant-see-all-fields-when-visualize-aggregation-terms-is-selected-in-kibana/78010/2 "2017-03-09T19:35:38Z")
It sounds like the mapping of the Name and Category field is mapped as `text` which is the field type used for search analysis, not aggregations. In 2.x this would have worked, but would be very inefficient since it uses field data. In 5.x, field data is disabled in ES. You can check this yourself by looking at the mapping in Dev Tools Console: ```auto GET my_index/my_type/_mapping/field/Name ``` In order to use the field for aggregations, the `type` should be `keyword`. See: [Text type family | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/text.html) > ...Text fields are not used for sorting and seldom used for aggregations (although the significant terms aggregation is a notable exception). > If you need to index structured content such as email addresses, hostnames, status codes, or tags, it is likely that you should rather use a keyword field. --- _[View the full topic](https://discuss.elastic.co/t/cant-see-all-fields-when-visualize-aggregation-terms-is-selected-in-kibana/78010)._