Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
MigueldelCampo
Contributor III
Contributor III

New Write Table feature

In the new Write Table functionality, is there a way for each user who logs into the application to see their own annotations? I don't understand the concept.

Labels (2)
1 Solution

Accepted Solutions
marksouzacosta

Hi @MigueldelCampo,

By default, write-back data is visible to all users; it is not restricted to the original author.

However, you can manage data visibility by implementing Section Access or other standard Qlik security mechanisms. This allows you to restrict write-back data at the row level, just as you would with any other Qlik-loaded data source.

To help you get started, I’ve recorded two videos covering the setup and advanced workflows:


Native Qlik Write Back is Here: Store to Snowflake & QVD
https://www.youtube.com/watch?v=B50XAm3yJMg
– An overview of the core functionality.

Bypass the 90-Day Limit: Incremental Load for Qlik Write Back
https://www.youtube.com/watch?v=Ejp1I3Hts_g
– How to manage long-term data retention.

 

Regards,

Mark Costa

 

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

View solution in original post

4 Replies
marksouzacosta

Hi @MigueldelCampo,

By default, write-back data is visible to all users; it is not restricted to the original author.

However, you can manage data visibility by implementing Section Access or other standard Qlik security mechanisms. This allows you to restrict write-back data at the row level, just as you would with any other Qlik-loaded data source.

To help you get started, I’ve recorded two videos covering the setup and advanced workflows:


Native Qlik Write Back is Here: Store to Snowflake & QVD
https://www.youtube.com/watch?v=B50XAm3yJMg
– An overview of the core functionality.

Bypass the 90-Day Limit: Incremental Load for Qlik Write Back
https://www.youtube.com/watch?v=Ejp1I3Hts_g
– How to manage long-term data retention.

 

Regards,

Mark Costa

 

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

chriscammers
Partner Ambassador
Partner Ambassador

I did some experimenting with the same question here is what I did.

Add your write table with whatever dimensions you want to use as the primary key then create an additional dimension with the following formula.

=valuelist(GetUserAttr('userEmail'))

 

This formula will give you a field with the value of the user's email address. This will be self limiting because the result of the formula will be the same unless you do some major updating to the user identity fields in the repository.

Now in your change store create the primary key including the email address field.

Lastly add your editable fields and you will have a write table with private comments for each user.

 

Now when you do this the change store will grab the formula as the column heading so that could be a bit of an issue when you retrieve the results and attempt to save them off to an external data store.

 

Screenshot 2025-12-19 133439.png

MigueldelCampo
Contributor III
Contributor III
Author

Thanks a lot!!!

numensrl_it
Contributor
Contributor

Hi,

We are very interested in the new feature. We have tried it on a customer tenant, but we cannot find it in our own company tenant that we use for demos. Our subscription is Capacity Model - SaaS - Standard. Are there any limitations for this feature?

Thank you