# Visualisation don't work even after recreating index templates **URL:** \ **Category:** Kibana\ **Created:** [March 30, 2018, 9:24pm UTC](https://discuss.elastic.co/t/visualisation-dont-work-even-after-recreating-index-templates/126286 "2018-03-30T21:24:12Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\ **Post date:** [March 30, 2018, 9:31pm UTC](https://discuss.elastic.co/t/visualisation-dont-work-even-after-recreating-index-templates/126286/2 "2018-03-30T21:31:11Z")
The problem is that the id of the index pattern changed when you recreated it. In the past, the `id` for all saved objects was just their name, so your old `elastiflow-*` pattern had the same ID. Likewise, all the saved objects that referenced it (visualizations and saved searches) used that value for their `index`. Some time ago, Kibana switched to using UUID strings for the value to allow for saved objects with the same name (mostly to enable multiple index patterns with the same pattern). Your new index pattern in `elastiflow-*`, but the `id` in Elasticsearch is going to be some UUID value, which you'll have to look up. Once you know that value, you have 2 options: - Change the `id` of the index pattern to `elastiflow-*` - Change the `kibanaSavedObjectMeta.searchSourceJSON.index` value in all of your saved visualization objects to match the UUID of the index pattern --- _[View the full topic](https://discuss.elastic.co/t/visualisation-dont-work-even-after-recreating-index-templates/126286)._