Discussion board where members can get started with Qlik Sense.
Rebumping this thread.
Reading on Qlik Tips
there was discussion on duplicating the app taking ownership and then republishing, but that method does not seem to work either. Really looking for a solution on this as none of the QMC approaches seem to work as of 3.1.....
I am missing something too. If I duplicate app and view it in my Work, I see the added sheets as if they were any sheet in an unpublished app, but upon publishing (replacing) the sheets revert to Not Approved and appear in community sheets.
My other point on this is that if we mess with repository db on any node (whther that is central or otherwise) the repositories will no longer sync up correctly. Not sure I would want to go down that road anyway if we can get a workable QMC sollution.
So I figured it out. So just in case anybody else has the question...
In QMC, Duplicate the app and change ownership to you.
Open the app in the hub under My Work
Duplicate the sheets that you wish to approve. You can then optionally delete the original community sheets.
Go back to QMC, publish the app, replacing the one that is in the stream.
Now the Community Sheet will be in the main app. Yeeah!
Sorry Aaron - when you replace an app, only the data model gets updated, no front-end changes. Can you confirm this is the case?
When you replace the app, any changes you made while in work will also be migrated to your published stream. And the "community" sheets that I duplicated in work are now part of the main app because they were replicated while in work and then published.
All this jargon is confusing!!!
That's interesting - I had a different experience. What happens to the community and personal sheets? Do they get lost as your app in your MyWork environment will not have them?
delayed answer, but the best (to my knowledge) method for Publishing Community Sheets to Base Sheets is to use the QMC Utilities: Qlik Sense QMC Utilities
I have also successfully tested the Sheet Publishing with the QMC Utilities in a multi-node environment.