# 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/70034>\
**Category:** Kibana\
**Created:** [December 27, 2016, 5:13am UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70034 "2016-12-27T05:13:44Z")\
**Posts on this page:** 1\
**Showing post:** 16

<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 4, 2017, 3:31pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70034/16 "2017-01-04T15:31:26Z")

</div>

Can you also run

```auto
GET metricbeat*/_mapping/metricsets/field/system.load.norm.15

```

and

```auto
GET /_field_stats?fields=system.load.norm.15

```

in dev tools and send me the output?

Refreshing the field list in management (the yellow button) should correct those fields to be marked as searchable and aggregatable, unless their is an issue with no data existing for those fields.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/0/017ddd21f52af6781c2a809d58aa0d18a3dc24b4.gif)

---

_[View the full topic](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field-visualize-field-is-a-required-parameter/70034)._