Troubleshooting - Write table
This help topic provides guidance for common errors you can encounter when working with write tables.
Write table displays as invalid visualization
When you open a sheet that contains a write table, the write table is not displayed. Instead, an error message displays Invalid visualization.
Possible cause 1
You have been given access to the app, not the space containing the app. The write table does not support fine-grained access control. See Sharing apps with users who are not space members.
Proposed action 1
The space owner or manager must give you the required access to the space containing the app with the write table. For the specific space roles, see Space permissions.
Possible cause 2
You do not have the required space role to view or use the write table.
Proposed action 2
The space owner or manager must give you the required access to the space containing the app with the write table. For the specific space roles, see Space permissions.
Possible cause 3
An administrator has not assigned you the required permissions for working with write tables.
Proposed action 3
Contact your tenant administrator and request to be assigned the required value for the Manage write table charts permission.
For more information, an administrator can refer to:
-
Setting permissions for write tables (capacity-based subscriptions)
-
Setting permissions for write tables (user-based subscriptions)
Error in editable columns
An error in editable columns is shown. The error could be any of the following:
-
The write table does not support duplication. Please delete this object.
-
Unable to connect to change store.
Possible cause 1
The write table does not support duplication. Duplication happens in any of the following cases:
-
A sheet or app containing a write table is copied and pasted, or duplicated.
-
A write table visualization is copied and pasted.
-
You export an app containing a write table and then import the app back into Qlik Cloud.
-
You duplicate a write table using enigma-js.
For more information, see Change store and data retention.
Possible cause 2
The underlying change store for the write table does not exist.
Proposed action
Recreate the write table by configuring a new chart. For more information, see Creating write tables.