topic Re: Section Access Causing Filter Reset in Qlik App Write-Back Functionality in QlikView

Section Access Causing Filter Reset in Qlik App Write-Back Functionality

JuMo — Fri, 31 Oct 2025 05:42:23 GMT

Hello,

I've added write-back functionality to my Qlik App using a WriteBack Table. On my page, there are several filters (like month and year), and when I save my write-back, a partial reload occurs. After this, I can continue editing the data (or not).

Everything functioned perfectly until I recently implemented section access. Now, after each write-back and partial reload, my filters are cleared, and the user has to re-select the values. This significantly slows down the editing process, although the write-back itself still works perfectly. Do you have any recommendations to address this issue ?

Hint, if I remove the reduction table from my Load I don't have this problem, but of course the Section Access is useless then.

Re: Section Access Causing Filter Reset in Qlik App Write-Back Functionality

JuMo — Fri, 07 Nov 2025 08:30:13 GMT

No one is inspired by this one ? 🙂

Re: Section Access Causing Filter Reset in Qlik App Write-Back Functionality

marcus_sommer — Fri, 07 Nov 2025 12:01:09 GMT

I'm not sure if the lost of the selection state could be prevented with any measurement.

But there may some workarounds. For example if the data aren't absolutely confidential the section access might be replaced with selections against the user and/or conditions within the expressions, like:

sum({< User = {"$(=osuser())"}>} Value

Another attempt may be to set the current selection to a bookmark before triggering the write-back and restoring the state with it later.

Further there might be other write-back methods which don't need a reload else pushing the data directly into a data-base.