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

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
cancel
Showing results for 
Search instead for 
Did you mean: 
Ormesome
Contributor III
Contributor III

Trouble with implementing writeback

I am following the instructions here (Video ‒ Creating a basic write-back example with Qlik Cloud | Qlik Help) for implementing writeback.

The variables are being passed through to Automations with the value in the dataset and not the values entered into the variable input object.

The update worked if I create unbound variables by removing the definition of the variable, but the variable input objects will not update to have the value of the selected data row before being edited.

How do I bind my variables to both the dataset and the variable input object AND have the values passed to the automation?

2 Replies
NS_Qlikupdates
Partner - Creator
Partner - Creator

This is a common issue with variable inputs in Qlik Automations, where the dataset values are passed instead of the actual user-entered values from the variable input object. This can cause inconsistencies during the writeback process.

A more reliable approach is to avoid heavily variable-dependent flows and use a direct writeback method instead. Solutions like SenseOps Writeback capture user inputs directly from the UI, helping reduce these mismatches and making the writeback process more reliable and easier to manage.

Quick Links:

Know More

Try for free

Sunilsahu_345
Contributor III
Contributor III

One thing worth checking is whether the automation is reading the variable values before the variable input object has completed updating. In some writeback implementations, the automation can receive the original bound field value instead of the latest user-entered value if the trigger sequence is not synchronized correctly.

It may also help to verify whether the variables are being updated through an action before the automation is called, and whether the variable input object is truly writing to the same variable that the automation expects. Testing with a simple text object that displays the variable value immediately before triggering the automation can sometimes help identify where the mismatch is occurring.

Have you been able to confirm that the variable values shown in the UI are the same values being passed into the automation execution logs?