Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I’m working with Qlik Cloud Automate and I’m trying to update the same variable (e.g. vAlert) across multiple apps.
For example:
I loop through a list of App IDs
For each app I try to Update Variable
In some apps the variable exists → update is successful
In other apps the variable does NOT exist → I get a Warning (not an error)
This part works as expected.
What I’m missing / stuck on:
After the automation finishes, I want to get a final summary, showing:
which apps were updated successfully
which apps failed because the variable does not exist
Ideally something like:
App A – OK
App B – variable does not exist
App C – OK
App D – variable does not exist
The output source can be anything (email, table, app, report), I can always change it, but I don't know how to get this information.
Please help 🙂
Hi @Sebastian_Dec ,
You can create a List variable - I called logMessage - and add any item log you need. This is a sample:
With the variable populated you can output it to see the results at the end of the Automation, or send by email - even creating a HTML email body message, etc.
Regards,
Mark Costa
Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hi @marksouzacosta, thank you for the suggestion — using a List variable (e.g. logMessage) to store the final summary definitely makes sense and solves the output part of the problem -> displaying r esults.
What I was actually missing, though, was not where to store the summary, but how to reliably determine whether the variable update was successful or failed because the variable does not exist.
Since Update Variable only raises a warning and does not expose a structured success/failure flag:
I had to add an explicit pre-check (e.g. List Variables per app and verify the variable name) to decide:
- update + log OK
- log variable does not exist
(This is the solution:
Checking if a variable exists in the List Variables, if so, changing the IFEXIST variable to 1.
Nest Condition, if IFEXIST = 1, UpdateVariable + logMessage
IFEXIST = 0, only logMessage)
Once that logic is in place, your approach with a List variable works perfectly for building the final summary 🙂
Hi @Sebastian_Dec ,
You can create a List variable - I called logMessage - and add any item log you need. This is a sample:
With the variable populated you can output it to see the results at the end of the Automation, or send by email - even creating a HTML email body message, etc.
Regards,
Mark Costa
Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hi @marksouzacosta, thank you for the suggestion — using a List variable (e.g. logMessage) to store the final summary definitely makes sense and solves the output part of the problem -> displaying r esults.
What I was actually missing, though, was not where to store the summary, but how to reliably determine whether the variable update was successful or failed because the variable does not exist.
Since Update Variable only raises a warning and does not expose a structured success/failure flag:
I had to add an explicit pre-check (e.g. List Variables per app and verify the variable name) to decide:
- update + log OK
- log variable does not exist
(This is the solution:
Checking if a variable exists in the List Variables, if so, changing the IFEXIST variable to 1.
Nest Condition, if IFEXIST = 1, UpdateVariable + logMessage
IFEXIST = 0, only logMessage)
Once that logic is in place, your approach with a List variable works perfectly for building the final summary 🙂