# Setting default app and import/export seem broken in kibana 5.6.3

**URL:** <https://discuss.elastic.co/t/setting-default-app-and-import-export-seem-broken-in-kibana-5-6-3/103400>\
**Category:** Kibana\
**Created:** [October 10, 2017, 3:20pm UTC](https://discuss.elastic.co/t/setting-default-app-and-import-export-seem-broken-in-kibana-5-6-3/103400 "2017-10-10T15:20:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rumbles](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rumbles/32/5946_2.png) [@Rumbles](https://discuss.elastic.co/u/Rumbles)\
**Post date:** [October 10, 2017, 3:20pm UTC](https://discuss.elastic.co/t/setting-default-app-and-import-export-seem-broken-in-kibana-5-6-3/103400/1 "2017-10-10T15:20:43Z")

</div>

I used to be able to set the default landing page by using kibana.defaultAppId in the kibana.yml file, but if I use:

kibana.defaultAppId: "dashboard/Default"

After creating my dashboard called Default, this doesn't work, as kibana is looking for the id instead of the human readable name, and since that is generated by the application, it is different from host to host (I have around 10 different machines running kibana as they have to be in isolated environments - I would like config managed by salt to be the same on all, not have to keep a record of each id to ensure it keeps working).

Similarly, if I export the searches, visualisations and dashboards from one environment, I cannot import them in to another environment as the id for the index key, searches and visualisations are different from the other environment are different and nothing will import. The dashbaord that are imported are also broken as they're looking for ids that won't ever exist.

This used to work fine in kibana 4, is there any way to make this work in kibana 5? Or am I forced to manually configure each server if I want to upgrade it from kibana 4?

---

<div class="post-metadata">

**Author:** ![Rumbles](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rumbles/32/5946_2.png) [@Rumbles](https://discuss.elastic.co/u/Rumbles)\
**Post date:** [October 11, 2017, 10:03am UTC](https://discuss.elastic.co/t/setting-default-app-and-import-export-seem-broken-in-kibana-5-6-3/103400/2 "2017-10-11T10:03:00Z")

</div>

nevermind, seen:

> [@Is export/import of Saved Objects broken?](https://discuss.elastic.co/t/is-export-import-of-saved-objects-broken/100958/4):
>
> Thanks Mark. Yes, that's what it looks like. Couple of questions I had though: Why did I get different pattern IDs (alias name vs auto generated ID) when I exported the same object twice? How to view the auto-generated pattern ID? I couldn't find any way for this. If I could then i would have edited the json to use that instead. -Thanks Nikhil

and subsequently:

> <https://github.com/elastic/kibana/issues/13359>
>
> In https://github.com/elastic/kibana/pull/12719 we moved to using a unique IDs f…or the index pattern, as opposed to the pattern itself. This allows for editing the pattern, but brought more light to an existing issue when an object is imported referencing an index pattern which does not exist.
> 
> \<img width="1143" alt="screenshot 2017-08-06 23 18 58" src="https://user-images.githubusercontent.com/40265/29014399-abdc53c2-7afd-11e7-80d8-0b4015a4e2b4.png"\>
> 
> Previously, when the pattern was the ID, you could create the missing pattern and re-run the import.
> 
> Now that we reference the index pattern by ID, we have added a link to the error to pre-fill an advanced setting with the ID. This forces the index pattern to be created with the ID provided.
> 
> \<img width="944" alt="screenshot 2017-08-06 23 22 40" src="https://user-images.githubusercontent.com/40265/29014503-2995a278-7afe-11e7-8c5f-8f217ccfdb1c.png"\>
> 
> The only difference from this point is you need to know the pattern as it was previously provided for you. Given you know what the expected pattern is, you can provide it and create the index pattern. The imported saved object will then work.
> 
> If the pattern required already exists and you attempt to create a new index pattern with the same name, you will be presented with a modal to edit the pattern instead.
> 
> \<img width="1143" alt="screenshot 2017-08-06 23 27 03" src="https://user-images.githubusercontent.com/40265/29014635-e2728b62-7afe-11e7-8cc6-476673deb1a6.png"\>
>  
> There is not a simple way to resolve this. You can update the JSON file being imported to replace the index pattern ID with your existing index pattern ID. You could also delete the existing index pattern, though that is not likely an option for users already using Kibana and the index pattern would be associated with other objects.
> 
> One idea is to not prevent the user from importing saved objects if the index pattern is missing. This behavior is actually inconsistent for object dependencies like visualizations or saved searches. For those, we provide an error when you attempt to load the object, not import it. With this, we could also allow the user to easily change the index pattern as opposed to using the JSON editor.

Testing whether it is fixed in 5.6.3, I installed 3 nodes on the same day and 2 had 5.6.2, the last had 5.6.3, so I must have spanned the release time

---

<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:** [November 8, 2017, 10:03am UTC](https://discuss.elastic.co/t/setting-default-app-and-import-export-seem-broken-in-kibana-5-6-3/103400/3 "2017-11-08T10:03:18Z")

</div>

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