# Kibana 5.2, How to set "searchable" or "aggregatable"

**URL:** <https://discuss.elastic.co/t/kibana-5-2-how-to-set-searchable-or-aggregatable/74810>\
**Category:** Kibana\
**Created:** [February 12, 2017, 2:36pm UTC](https://discuss.elastic.co/t/kibana-5-2-how-to-set-searchable-or-aggregatable/74810 "2017-02-12T14:36:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![allegro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/allegro/32/15441_2.png) [@allegro](https://discuss.elastic.co/u/allegro)\
**Post date:** [February 13, 2017, 2:02pm UTC](https://discuss.elastic.co/t/kibana-5-2-how-to-set-searchable-or-aggregatable/74810/4 "2017-02-13T14:02:03Z")

</div>

Thanks, warkolm.  
I changed the mappings as below.

```
{
  "mappings": {
    "logs": {
      "_source": {
        "enabled": true
      },
      "_all": {
        "enabled": true
      },
      "properties": {
        "id": {
          "type": "integer"
        },
        "timestamp": {
          "type": "date"
        },
        "customer_id": {
          "type": "integer"
        },
        "customer_name": {
          "type": "keyword"
        },
        "description": { 
          "type": "string",
          "index": "analyzed"
        }
      }
    }
  }
}

```

but situation is not changed. Kibana still cannot set the status to searchable.

In case, I cannot use the non-searchable field in dashboards.

Any idea?

---

_[View the full topic](https://discuss.elastic.co/t/kibana-5-2-how-to-set-searchable-or-aggregatable/74810)._