# Saved “field” parameter is now invalid. Please select a new field. …. Visualize: “field” is a required parameter

**URL:** https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667
**Category:** Kibana
**Created:** [January 5, 2017, 10:51am UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667 "2017-01-05T10:51:18Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![krishmah](https://avatars.discourse-cdn.com/v4/letter/k/d78d45/32.png) [@krishmah](https://discuss.elastic.co/u/krishmah)
#### Post date: [January 5, 2017, 10:51am UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667/1 "2017-01-05T10:51:18Z")

</div>

Hi All,

I am getting the error as Saved “field” parameter is now invalid. Please select a new field. …. Visualize: “field” is a required parameter

On further debugging , I am seeing that there are certain fields marked as Aggregatable and Searchable and it appears that it is being used by Kibana strictly to allow Count Distinct Aggregations only on fields defined as Aggregatable.

Any idea how does it classify a field as Aggregatable? I have following field and it does not appears as Aggregatable in the Kibana UI. Any idea what could trigger this. I already have data loaded and indexed and data contains this field.

```
				 "movie_id": {
						"index": "not_analyzed",
						"type": "string",
						"fields": {
							"hash": {
								"type": "murmur3"
							}
						},
						"doc_values": false
					},
```

---

<div class="post-metadata">

### Author: ![Stacey\_Gammon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stacey_gammon/32/14025_2.png) [@Stacey\_Gammon](https://discuss.elastic.co/u/Stacey_Gammon)
#### Post date: [January 5, 2017, 2:46pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667/2 "2017-01-05T14:46:25Z")

</div>

This is a known issue with the murmur3 field type that will be fixed in 5.2

PR:

> <https://github.com/elastic/elasticsearch/pull/21821>

  
Issue:  

> <https://github.com/elastic/elasticsearch/issues/21952>

---

<div class="post-metadata">

### Author: ![krishmah](https://avatars.discourse-cdn.com/v4/letter/k/d78d45/32.png) [@krishmah](https://discuss.elastic.co/u/krishmah)
#### Post date: [January 5, 2017, 5:15pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667/3 "2017-01-05T17:15:57Z")

</div>

Thanks Stacy. Was this something introduced recently. We remember using the same functionality in 5.0 Alpha4 release and we did not see this issue during that time. Can you please confirm?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 2, 2017, 5:16pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70667/4 "2017-02-02T17:16:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.