# Unable to parse imported visualizations on version 5.2.0 **URL:** \ **Category:** Kibana\ **Created:** [February 6, 2017, 3:51pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087 "2017-02-06T15:51:35Z")\ **Posts on this page:** 17\ **Page:** 2
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [February 28, 2017, 10:54am UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/21 "2017-02-28T10:54:18Z")
@avivc @jmaelbrancke@Terence_Chuen this fix is going to be part of [5.2.2](https://www.elastic.co/guide/en/elasticsearch/reference/current/release-notes-5.2.2.html) and it should be available for download rather soon from [https://www.elastic.co/downloads/elasticsearch](https://www.elastic.co/downloads/elasticsearch) ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [February 28, 2017, 12:03pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/22 "2017-02-28T12:03:26Z")
Thanks @Brandon_Kobel 😁 Is there an estimated date ? ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [February 28, 2017, 12:10pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/23 "2017-02-28T12:10:58Z")
@avivc we don't announce release dates internally or externally because so many different things can cause these to shift. I'll update this ticket if I hear anything else. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [February 28, 2017, 12:12pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/24 "2017-02-28T12:12:40Z")
Fair enough! Tnx ---
**Author:** ![Terence\_Chuen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/terence_chuen/32/13956_2.png) [@Terence\_Chuen](https://discuss.elastic.co/u/Terence_Chuen)\ **Post date:** [February 28, 2017, 12:53pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/25 "2017-02-28T12:53:38Z")
Thank you for notifying,I will check repo and update. I will report here again after the update. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [February 28, 2017, 5:12pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/26 "2017-02-28T17:12:54Z")
@avivc @Terence_Chuen 5.2.2 is available now. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [March 1, 2017, 5:50am UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/27 "2017-03-01T05:50:39Z")
Tnx @Brandon_Kobel Do I have to upgrade both ES and Kibana to 5.2.2 to acquire the changes? ---
**Author:** ![Terence\_Chuen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/terence_chuen/32/13956_2.png) [@Terence\_Chuen](https://discuss.elastic.co/u/Terence_Chuen)\ **Post date:** [March 1, 2017, 6:29am UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/28 "2017-03-01T06:29:36Z")
@avivc I think it should be. The version of all packages should be consistent. @Brandon_Kobel I upgraded and tested, the function has returned to normal. Thank you. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [March 1, 2017, 8:41pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/29 "2017-03-01T20:41:39Z")
@avivc you'll want to keep the version of ES/Kibana in sync to ensure you don't hit any compatibility issues. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [March 1, 2017, 9:04pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/30 "2017-03-01T21:04:28Z")
Tnx @Brandon_Kobel ---
**Author:** ![Vinoth\_Ravi](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@Vinoth\_Ravi](https://discuss.elastic.co/u/Vinoth_Ravi)\ **Post date:** [March 1, 2017, 10:26pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/31 "2017-03-01T22:26:20Z")
I think this can be worked around by tying up the visualization to a search , and include the regular expression as part of the search . Refactor all index based visualization to depend on a search instead and have the regex filter as a part of search query. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [March 2, 2017, 7:35am UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/32 "2017-03-02T07:35:47Z")
@Vinoth_Ravi do you mean - **Taking the visualize json request and add it regex** `OR` **Export data from the dev tools (myIndex/\_search) and add it regex for the new query** **?** You have an example for this? It is possible to double-click on entity in visualize and it open an action bar to filter data Tnx 👍 ---
**Author:** ![Vinoth\_Ravi](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@Vinoth\_Ravi](https://discuss.elastic.co/u/Vinoth_Ravi)\ **Post date:** [March 2, 2017, 5:13pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/33 "2017-03-02T17:13:07Z")
Lets say we have an export of all the search, viz and dashboard objects from kibana 5.1.2. Import this into 5.2.1 by any means - either directly putting it in .kibana index or import ( if it succeeds ). grep for "exclude" "include" keywords from the export.json and find 'affected' viz. Open each of the affected viz, remove the regex pattern from "include/exclude" and add it to the search bar at the top. For example, if field\_1 has regex include like .\*ERROR.\*|\*.WARN.\* , remove it and place in the search at the top as field\_1: \*ERROR\* OR field\_1: \*WARN\*. ( Note if the viz was already linked to a search, double click to unlink it and edit the search tab directly). I tried this and it works okay, but only 10% of my Viz are affected ( which used exclude/include pattern ) so it is feasible workaround for me. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [March 4, 2017, 2:33pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/34 "2017-03-04T14:33:00Z")
Cool @Vinoth_Ravi ! For what you have tried, does it stays for good? I mean, once you've add the regex to the search field instead in the include/ exclude box.. In that case it case be useful, but if not it might be a beat tedious right ? ---
**Author:** ![Vinoth\_Ravi](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@Vinoth\_Ravi](https://discuss.elastic.co/u/Vinoth_Ravi)\ **Post date:** [March 6, 2017, 2:17am UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/35 "2017-03-06T02:17:42Z")
Yes, the fix is clean. ---
**Author:** ![avivc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avivc/32/16501_2.png) [@avivc](https://discuss.elastic.co/u/avivc)\ **Post date:** [March 6, 2017, 2:01pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/36 "2017-03-06T14:01:59Z")
Great @Vinoth_Ravi ! Is it good to determine permanent **json input** too? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 3, 2017, 2:02pm UTC](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087/37 "2017-04-03T14:02:00Z")
Closed on April 3, 2017, 2:02pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/unable-to-parse-imported-visualizations-on-version-5-2-0/74087.md?page=1)