Maintaining Sheet URLs When Moving Public Sheets to Community Section in Qlik Cloud

[nammaitran]

I hope you are all doing well!

I’m on an urgent need of seeking a way to move public sheets back to the community section in Qlik Cloud without changing their ID and URL.

Here’s the situation:
I exported an application containing 40 public core sheets and 200 community sheets into a QVF file. After republishing it in Qlik Cloud, all the sheets ended up in the public section, resulting in a total of 240 sheets. Now, users can’t unpublish and edit their dashboards.

I really need to move those 200 community sheets back to where they belong while keeping their URLs intact.

Any advice or insights would be greatly appreciated!

Also, is it normal for Qlik not to retain community sheets when publishing an application? This seems odd to me, and I’d love to hear if others have experienced this.

Thank you!

[nammaitran · Accepted solution]

Hello,

I was able to resolve the issue by moving the application from managed space to personal space, unpublishing the sheets meant for the community section, then moving the application back to managed space and republishing the sheets. The republished sheets are now converted into community sheets, allowing reuse by other users with the contributor role.

All of these operations can be done using command line:

Step 1: qlik app space update <application id> 

Step 2: qlik app object unpublish <sheet id> -a <application id> 

Step 3: qlik app space update <application id> --spaceId <space id of the managed space> 

Step 4: qlik app object publish <sheet id> -a <application id>

Keep in mind that when transferring an application from managed space to personal space, only core sheets and your private sheets are carried over. However, if you move the application back from personal space to managed space, any community sheets and other users's private sheets will be restored to their original state.

I found this feature of Qlik Cloud very interesting, but if someone isn't aware of the difference compared to Qlik On-Premise, it could lead to some unexpected issues with sheet management.

I hope that it would help anyone having the same issue.

Best regards,

Nam Mai TRAN

[rusnakpe]

Hi @nammaitran

I wanted to ask if the above solution is working for you. After publishing all the community sheets back within the managed space, the owner remains the user who imported the app unless you use the "Change Owner" CLI command. However, this can be problematic—you can only change the ownership of unpublished objects (so you need to unpublish them first), but republishing the object is only allowed for the object's owner. Additionally, it is unreal to switch context to all the respective owners of the objects for each CLI command.

If you've found a solution to this, could you please share it? I'm expecting the same ownership for the app and app objects as we had in the On-Prem solution, but this seems unrealistic due to the limitations I mentioned above.

Thanks!