Losing published/community bookmarks when updating the application

[alexis]

I have TWO issues relating to Bookmarks in a Qlik Sense on-premise installation:

Issue 1:

I am running Qlik Sense on-premise and I have a published application that a number of users are using.

The users are using Bookmarks extensively to run weekly reports etc and as they create these bookmarks they Publish them so that all the users can access them. These published bookmarks are visible to all users but appear as "Community bookmarks" (see below) instead of "Published bookmarks" as I would expect. The 1 "public" bookmark below is one that I created and published. Can someone explain this?

Issue 2:

The second, and more serious issue that I have is that I now have to make changes to the functionality of the application as well as make some bug fixes. From the QMC I exported the above published application (with data) to the server's disk and then imported it from QMC to work on in in my "Work" stream before publishing the new version.
When I imported the exported application I noticed that all the "Community" bookmarks had disappeared and all I had was the single "Public" bookmark that I had previously created.

Obviously, this is a show stopper and I am at my wit's end because the users do need the new version (with the bug fixes) but cannot work without their bookmarks. 
I have not encountered this issue in a SaaS environment which works a little different (Make the sheet you want to change "Private", make the changes and then "publish" the sheet and all the bookmarks are still there)

Can someone PLEASE throw some light onto this issue? 

[Mark_Little]

HI @alexis 

Issues 1 is just the way it works. Any bookmarks created by the dev and published will be the public bookmarks, where any created by users after will appear as Community.

Issue 2 is again how it works. if you export it and then reimport it it is given a new app id, so loses the connection to the Community stuff. My normal a approach is duplicate the app and then makes changes and publish over the top of the old, this keeps all community stuff. I would think as along as you publish over the live copy you should not lose anything

[Or · Accepted solution]

As explained by Mark, this is correct behavior in both cases.

* Bookmarks created by the developer (while the app is in their Work stream) are saved as part of the app and will appear as "My bookmarks" during development and as "Public bookmarks" when the app is published

* Bookmarks created in the published version of the app will be saved server-side and remain associated with the app ID regardless of whether or not the bookmark itself is private or published. Duplicating or exporting the app will result in a version without these bookmarks, since it generates a new app ID

* When you re-publish the app to the same ID (using the "Replace the existing app" option from hub or the "Replace existing app" option from QMC), all of the bookmarks will persist with the published app since it has the same ID

* If you delete the old app and publish a fresh one, you will lose the bookmarks as a new ID will be generated for the app

Note that this is true not just for bookmarks but for any number of other things - private sheets, stories, etc - so you should always republish to the same ID when editing an existing app.

[alexis]

Apologies for the delay in replying Mark but I have been unwell and was only able to re-test based on your reply and you were correct and all is well again. Although you were the first to respond, I have decided to award the "Accept as Solution" to "Or" as he was a little more detailed in his explanation. I thank you both for responding.
Cheers
Alexis

[alexis]

Thank you "Or". Although "Mark6505" responded first with an explanation, your more detailed response was particularly helpful and I thank you!