Using a Write table in a Dev / Prod Environment

WeLoveQlik — Thu, 12 Mar 2026 12:16:24 GMT

Hello everyone,

I typically structure my Qlik Cloud environments with a Development (shared) space and a Production (managed) space.

Recently, I’ve been receiving more requests to implement WriteTables for writeback functionality, and overall they have been working well.

However, I’ve run into a challenge during the publish process. When I publish an app from Development to Production, the Change Store value changes, which causes any writeback data created during development to disappear.

In many cases, I would like to prepopulate writeback values during development so that they already exist for users once the app is published. At the moment, there doesn’t seem to be an obvious way to carry those values over.

Has anyone found a good approach for:

Preserving WriteTable data when publishing apps
Prepopulating writeback values before moving an app to Production
Managing writeback data across Development and Production spaces

Any suggestions or best practices would be greatly appreciated.

Thank you!

Re: Using a Write table in a Dev / Prod Environment

amonjaras_c40 — Mon, 23 Mar 2026 16:10:58 GMT

Hello!

I solved this with an automation, using the List Change Stores block. It will give you the primary key, space ID, chart ID and app ID of every change store in your tenant.

Just run the automation after you publish an app containing your write table.

Hope this helps!

topic Using a Write table in a Dev / Prod Environment in App Development

Using a Write table in a Dev / Prod Environment

Re: Using a Write table in a Dev / Prod Environment