Skip to main content Skip to complementary content
Close announcements banner

Troubleshooting - Working in spaces

This page suggests solutions to common issues you might encounter when working in shared and managed spaces.

A load script needs to be updated, but the app owner is unavailable

In a collaborative setting, there might be times when a data load script needs to be updated but the app owner is not available.

Space managers (users with the Owner or Can manage role in the space) can assign permissions to an eligible user to manage the load script.

Try one of the following:

  • Assign the Can edit data in apps role to specific users in the shared space. These users will be able to edit the load script or manage the data.

  • Duplicate the app. When you duplicate an app, you become the owner of the new copy.

For both of the above solutions, users need access to the data sources used in the app or script to be able to reload it. If they do not have access, contact a tenant administrator move or change ownership of any required data sources, or provide the required space permission to access the data sources. New credentials need to be entered when editing a connection.

For more information, see Managing data connections.

The source app for a published app was deleted

If the source app for an app in a managed space is deleted, the published copy of the app cannot be updated and republished as needed.

You need to re-establish the parent-child relationship between a source app and the published app. You can do this by saving a backup copy of the published app, then re-publishing this backup copy from a personal or shared space.

  1. Export the published copy of the app without data.

    Exporting apps from managed spaces

  2. Re-upload the app to a personal or shared space.

  3. Publish the app back to the same managed space, with the same name as the existing published app.

    When prompted, select Replace to replace the existing published copy of the app.

I made changes to the roles of space members, but their access has not changed

When you make any changes to user's permissions for apps or scripts, these changes are not instantly reflected in actively opened apps and scripts. To ensure that the changes to the user's permissions are updated, the user must close all browser tabs belonging to the affected app or script and wait at least two minutes (app session's Time To Live), then re-open the app. This applies to app and script permissions in personal, shared, and managed spaces. Changes in permissions for newly opened apps are reflected instantly.

The owner of a space, app, or other entity has left the tenant

When a user is deleted from Qlik Cloud, such as when a user leaves an organization, assets they own will no longer have an owner. This can cause app and script reloads to fail, and cause other access issues.

A tenant administrator can reassign ownership of spaces, apps, scripts, and data connections. As a side note, analytics administrators and data administrators can perform similar management tasks in shared and managed spaces, and data spaces, respectively.

Contact your tenant administrator to inquire about reassigning ownership of assets, and moving them to other spaces as needed.

For more information, see:

Backing up content added to published apps in managed spaces

After an app is published to a managed space, space members can create new sheets and visualizations in the published copy.

If a published app is deleted, the content that has been added to it since it was published cannot be recovered.

As a preventative measure, it is recommended to frequently create backup copies of the published app. From the Qlik Cloud Analytics hub, use the Export without data option. Another best practice is to periodically copy important Community sheets from the published app, and paste them into the source app. The sheets can be made public before republishing to add them as base content in the app.

If the app is ever deleted, it can be republished from the source app, or the backup copy can be uploaded to the development space then published back to the managed space.

For more information, see Exporting apps from managed spaces.

I built an app using a data source in another space, but I have lost access to that space

When working in a shared space, you can build analytics content in a shared space using data sources from other spaces. If you lose access to any of the spaces containing the data sources, you might encounter reload failures and access issues.

As a first step, confirm that you have indeed lost access to the spaces in which the sources are located. If this is the case, you can:

  • If the access issues are caused by the space owner leaving the tenant (deleted as a user), contact a tenant administrator to reassign ownership and move the data sources as needed. User credentials will be required to edit data connections.

  • Consider recreating any data connections yourself.

I am the space owner, but I cannot create ML resources and business glossaries

In addition to space permissions, there are additional security roles that are required to work with AutoML and business glossaries.

For full AutoML access, you need the Automl Experiment Contributor and Automl Deployment Contributor roles. For most business glossary actions, you need the Steward role.

Security roles can only be assigned by an administrator. Contact your tenant admin to learn more.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!