Macros/Actions triggering other Macros/Actions
Article Number: 000003078 | Last Modified: 2019/09/25
In Qlikview it is possible to create an Action or Macro that will trigger on certain user behavior in an application, such as making selections or switching sheets. It is also possible to create a Macro/Action that will in itself perform an action that could trigger another such Macro/Action.
An example would be to create a user triggered Action that changes the current active sheet, and then adding an Action that is triggered by switching to that sheet.
These macros may fail in a deployment, especially once deployed on the QlikView server.
The stability and functionality of macros in the QlikView environment is depended on the nature of the macros and actions as well as their complexity. Qlik advises against deploying macros, as compatibility cannot be guaranteed.
Limitations in clients like AJAX, as well as changes done to use a variant of BNF for scripting (12.30 and up) will lead to macros failing. See
Example: In AJAX, macros and actions are run in a single thread on the QlikView Server. This can can result in them not being triggered properly if another Macro/Action is already running.
Depending on the complexity, this might work in the Desktop client or the Plugin.
Troubleshooting and coding of those macros fall outside of the support scope provided by Qlik and our best practice recommendation is to avoid using recursive or looping macros entirely to ensure the applications remain future proof.