Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel.
Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements.
Note - These instructions assume you have already created connections as required in Example 1.
This On-Demand Report Automation can be used across multiple apps and tables. Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
I'm facing an unexpected error after a long time without any errors, see below:
"error": "Error calling endpoint \"Microsoft Excel - Update Rows In Worksheet\"",
"name": "Update Rows In Worksheet",
"datasource": "Microsoft Excel"
"external error": true
until the block "Qlik Cloud Services - Get Straight Table Data" there is no errors.
The error comes with the block "Microsoft Excel - Create Excel Table With Headers".
I can't understand what could be the reason.
Anyone could help here?
Many thanks in advance for your time.
Hi @MattGrayndler ,
We have been using this extension for a while but it has just started corrupting the top of the sheet within the tenant when you either move the Extension onto a sheet or go to the sheet in question.
Is there an update that will correct this.
Same with us - its rather urgent and looks really bad...
btw - I hate extensions for that exact reason!!!!
Also just to add salt to the wound it looks like now there is new extension (instead of the old one https://github.com/rileymd88/automation-trigger ) which does not inherit settings from old form entries meaning we have to go back and update all objects where it was used. I didnt manage to get it working neither...
I have not been able to update the article since it was moved to this section of Qlik Community, so it's links and everything it mentions is accurate at Oct 2021.
I have tried to be active in the comments instead, where I have provided new versions of automations (that now support direct email) and some different logic depending on different use-cases.
The intent of the article has been to highlight what is possible with Qlik Application Automation, and encourage Qlik developers to extend and update as needed. And it's been great to see other users suggest ways to adapt the automation depending on different needs.
The extension I referenced was renamed Automation-Trigger late 2021, and there have been several enhancements and updates to this extension: https://github.com/rileymd88/automation-trigger/releases
If you are not leveraging the latest version of this extension, please do so.
I am currently not seeing any sheet formatting / usability issues with the latest version of this extension.
If you are, please let me know what region your tenant is in and I will check against your QCS instance.
I also have an update to the on-demand example as the extension has a new method to pass selections by creating a bookmark (this is how the native button also behaves).
You can download this update here: https://qliktechnologies365-my.sharepoint.com/:u:/g/personal/myg_qlik_com/EejVBX3IO3BDlaXX75v_OgcB-W...
If the sheet the extension is placed in only has one table, you don't need to add any measures. The automation will retreive the sheetID and find the first table object ID on the sheet. If there's multiple tables on the sheet (or the table exists elsewhere in the app) then continue to specify the Object ID as a measure.
There's no need to also add GetCurrentSelections() and DocumentName() - the extension now passes the AppID and BookmarkID.
You still need to add a form and a text input with a reference as 'Email'.
And now under Automation, select 'Include Selections'.
This example Automation will now email the file directly (taking advantage of Mail attachments that were added since this article was published).
The author of this extension has actually contributed to Qlik's open source native action button, and I am hopeful we will see native capability delivered to that button soon that enables this use-case.
I have been holding off asking the Qlik Community team to remove this article (and me publishing a new one) until this capability is native to Qlik and I can re-write the on-demand use-case without the need for an extension.
Hello there, Im getting this error constantly with that block, in every flow I try to use it...
Can I get some help? I really don't understand deeply the API's world 😞
Please post your query directly in our active Qlik Application Automation forum, which is being actively monitored.
All the best,
I appreciate the contribution, it is very helpful. In which part of the code can I change the Qlik image?