Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dec 24, 2025 4:52:48 AM
Dec 10, 2025 9:31:59 AM
This document contains frequently asked questions for the Qlik Write Table.
Content
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:
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.
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).
A: The write table is provided as an included capability.
A: No, the Write Table is only available in the following editions of Qlik Cloud:
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.
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.
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.
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.
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.
A: Text input box (manual user input) and dropdown (single select).
A: Not as of yet. For now, the values are a hardcoded list configurable in an editable column’s settings.
A: No, this is not supported and not on the roadmap.
A: Yes, we are planning to make the write table available in the government editions of Qlik soon.
A: No, the write table is only available on Qlik Cloud. There are no plans to make it available in on-prem versions.
Great FAQ and great release @Emile_Koslowski !
I made a video to guide new users on how to use the Write table and load data back into Qlik. Sharing it here:
https://www.youtube.com/watch?v=mZk_2v2m4U8
Hi @Emile_Koslowski,
I found an issue in the documentation page:
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Visualizations/WriteTabl...
The correct value is:
links/next/href
Regards,
Mark Costa
I have published a video showing how to store the Qlik Write back changes in Snowflake and QVD.
YouTube video:
https://youtu.be/B50XAm3yJMg
Data Voyagers post:
https://www.datavoyagers.net/post/native-qlik-write-back-is-here-store-to-snowflake-qvd
Regards,
Mark Costa
Hello @marksouzacosta
Thanks! I'm looking into the help site problem you reported.
All the best,
Sonja
Thanks @marksouzacosta! You are absolutely correct, an update is on it's way.
I am looking forward to exploring the this new table. The video by Gui_Approbato filled in some gaps in my knowledge and gave me all the info that I needed to pull Write Table data into the data load editor.
Hi, is it possible to save changes directly to Databricks instead of a QVD or Excel file? If so, is there a video that shows how to save to Databricks? Thanks!
Hi @Bel01234 I made a video showing how to save on Snowflake. To convert to Databricks, should be easy. Please let me know if you have any questions:
https://youtu.be/B50XAm3yJMg
Regards,
Mark Costa
It seems 'real-time' sync - means same input view with active session. This write-table is great!
We are greedy and want more 🙂
One more step forward could be referencing the input data in expression and refresh without having to reload the app - would be a 'real game-changer' !
My mistery with the "locked" input table on some environments has been solved, thanks to a linkedin post from eric mertens mentioning that the table becomes read-only if touch-screen mode is on