# Saved "field" parameter is now invalid. Please select a new field **URL:** \ **Category:** Kibana\ **Created:** [March 28, 2021, 4:33pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field/268598 "2021-03-28T16:33:36Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Tim\_Mobley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tim_mobley/32/94741_2.png) [@Tim\_Mobley](https://discuss.elastic.co/u/Tim_Mobley)\ **Post date:** [April 22, 2021, 8:38pm UTC](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field/268598/3 "2021-04-22T20:38:09Z")
Just wanted to follow-up in case others run across this. I believe the root cause was using a different version of Winlogbeat (7.9.3) than Elasticsearch (7.9.1). At any rate, I reached out to @ManuelF who had a [similar issue](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field/256413) and he gave me great advice. When I exported the visualizations I needed to also append **.keyword** to the fieldnames. Once I had done that and re-imported the visualization, I no longer got the "Saved 'field' parameter is now invalid." (Thank you @flash1293 for your reply - sorry for not getting back faster.) --- _[View the full topic](https://discuss.elastic.co/t/saved-field-parameter-is-now-invalid-please-select-a-new-field/268598)._