Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Apr 13, 2026 7:39:50 AM
Dec 10, 2025 9:31:59 AM
This document contains frequently asked questions for the Qlik Write Table.
Content
- Data and metadata
- Q: What happens to changes after 90 days?
- Q: Which data is stored in the change-store?
- Q: Is there an audit trail or a history?
- Pricing and packaging
- Q: Where can I find pricing information?
- Q: Is this available to all cloud editions of Qlik?
- Access and Permissions
- Q: Does the Can Edit space role automatically grant access to the Write Table?
- Q: Does the write table support section access?
- Q: Which permissions are required to read from the change-stores API?
- Q: Which permissions are required to use the Write Table chart?
- UI and Input Types
- Q: A Write Table chart suddenly became read-only (but loads successfully)
- Q: What input fields are available?
- Q: Can we use dynamic values for the dropdown input field?
- Q: Is the write table available on pivot tables?
- Deployment
- Q: Will the write table come to government editions of Qlik?
- Q: Will the write table come to on-prem versions of Qlik?
Data and metadata
Q: What happens to changes after 90 days?
A: After 90 days, changes will be permanently deleted from the change store and will no longer be available in the Write Table chart.
There are three options to set up a scheduled extraction of these changes:
- Use Qlik Automate to set up a scheduled sync of these changes to a database of your choice; see How to extract changes from the Change Store (Write Table) and store them in a database using Qlik A... for details.
- Or use Qlik Automate to sync changes to Excel files, see How to extract changes from the change store (Write Table) and store them in an Excel file using Qli... for details.
- Use Qlik Load Scripts to create a scheduled sync to load these changes into a QVD or the app's data model. See How to extract changes from the change store (Write table) and store them in a QVD
- Use the change-stores API directly in a tool of your choosing. The api specs are available here: https://qlik.dev/apis/rest/analytics/change-stores/
Q: Which data is stored in the change-store?
A: Every new change is appended to the change store, together with a primary key and the metadata to track which user made the change and when they made it.
Q: Is there an audit trail or a history?
A: When new changes are made, they are appended to the change store with a 90-day TTL (time to live). The write table displays the latest change in the chart, and you can hover a cell in the chart to see previous change values with the user's info and timestamp.
The full history of all changes can be retrieved through the List Change Store History block in Qlik Automate or through the /changes endpoint in the API (until their 90-day TTL expires).
Pricing and packaging
Q: Where can I find pricing information?
A: The write table is provided as an included capability.
Q: Is this available to all cloud editions of Qlik?
A: No, the Write Table is only available in the following editions of Qlik Cloud:
- Qlik Cloud Analytics Premium
- Qlik Cloud Analytics Enterprise
- Qlik Sense Enterprise SaaS
Access and Permissions
Q: Does the Can Edit space role automatically grant access to the Write Table?
A: No. Adding and configuring the Write Table in a sheet requires the Manage write table charts user permission. This permission is automatically enabled in the User default role. Tenant admins can manage the Default user role or create a custom role that includes this permission.
Q: Does the write table support section access?
A: Section access is applied only to data that is in use by the Qlik engine.
The records shown in a write table depend on the primary key, which is configured using engine data. Therefore, if the write table is used in an app that uses section access, the records shown in the table will be restricted by section access.
However, the write table interaction data, such as edits created during analysis sessions, are stored in a change store. This happens separately from the engine, meaning Section access is not applied on a change store or on the change-stores API.
Therefore, users with permission to read from the change-stores API will be able to read all data from a change store regardless of the Section access rules.
For additional details, see Section access limitations.
Q: Which permissions are required to read from the change-stores API?
A: Users with the full Manage write table charts permission can access the change-stores API and use it to read changes from change-stores they have access to. It is also possible to create an OAuth credential that has limited API access to the change-stores API. Assigning this limited access to a user is not yet possible.
Q: Which permissions are required to use the Write Table chart?
A: Users with the full Manage write table charts permission or the Read and write access only permission can use the Write Table chart to read and write changes through the chart.
See Write table permissions for details.
UI and Input Types
Q: A Write Table chart suddenly became read-only (but loads successfully)
A: Please make sure that Touch screen mode is disabled for your app. The write table is read-only when touch screen mode is enabled.
Q: What input fields are available?
A: Text input box (manual user input) and dropdown (single select).
Q: Can we use dynamic values for the dropdown input field?
A: Not as of yet. For now, the values are a hardcoded list configurable in an editable column’s settings.
Q: Is the write table available on pivot tables?
A: No, this is not supported and not on the roadmap.
Deployment
Q: Will the write table come to government editions of Qlik?
A: Yes, the write table is available in the government editions of Qlik.
Q: Will the write table come to on-prem versions of Qlik?
A: No, the write table is only available on Qlik Cloud. There are no plans to make it available in on-prem versions.
Hi @Bel01234,
I'm not experienced with Databricks and Qlik Automation Databricks blocks but I was able to achieve the same thing using the Call URL basic block to call Databricks endpoints to send SQL Statements - I'm sure there must be better ways to do that.
This is what I have done:
The Params in this Block works as Body parameters when you set the Method as POST.
You must have in hands your wharehouse id, catalog and schema. This is my statement to delete all records from the FILM_WB table:
TRUNCATE TABLE FILM_WB
This is the full JSON Body:
{
"statement": "TRUNCATE TABLE FILM_WB",
"warehouse_id": "your_warehouse_id_here",
"catalog": "playground",
"schema": "default"
}
Use the header to do a Bearer Authentication:
The second Call URL block is similar to the first one. The only change is the Statement. The block is inside the List Current Changes From Change Store block loop, so it will be executed for every record loaded there. The Statement parameter looks like this:
Regards,
Mark Costa
