Best Practice for using source filed vs Writeback fields in Qlik Sense Workflow Application

[SarveshKumar]

Hi Team,

I am working on a Qlik Sense workflow application where data is loaded from a single source file and split into multiple logical tables associated through: Key Delivery.

I am using Straight tables for source/master data display 
writeback tables for user updates
At the same time, users are expected to manually update operational fields through writeback tables.

My Question:

 can editable/writeback columns be reliably used as filter pane fields in Qlik Sense? 
or is it recommended that filters should only come from stable source/master data tables, while writeback tables should only store operational/manual update fields?

I would like to understand:

Best Practice
performance impact
data consistency
recommended enterprise design approach
Thanks

[marksouzacosta · Accepted solution]

Hi @SarveshKumar,

There is no restriction on using Writeback fields as filters in your applications, but you have to load the recorded values into your application - like a regular field.

So, your application will end with the writeback fields and writeback fields loaded into your application through the Load Script - as a regular field.

I made a video showing how you can load writeback data into your app:
https://youtu.be/B50XAm3yJMg?si=B-eEfoyLdBxtzJ4X

Regards,

Mark Costa

[SarveshKumar]

Thank you @marksouzacosta .

[SarveshKumar]

Hi @marksouzacosta ,

Just want to know what level of access do I need for the implementation of the writeback and establishing a connection and reloading them back to Qlik Sense.

Regards 

Sarvesh

[marksouzacosta · Accepted solution]

Those are the details about the permissions needed:
Reference: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Visualizations/WriteTabl...

Regards,

Mark Costa

[SarveshKumar]

@marksouzacosta ,
thank you for the help.

Regards

Sarvesh