Macros/Actions triggering other Macros/Actions
Article Number: 000003078 | Last Modified: 2018/06/12
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.
In some cases/clients this will work fine, but in others it will lead to problems.
This is working as designed. The reason for it is a combination of limitations in some clients and a conscious design decision to avoid recursive actions/macros.
In AJAX, Macros and Actions are run in a single thread on the QVS, which can result in them not being triggered properly if another Macro/Action is already running. In some versions of Desktop and Plugin it will work fine.
This functionality will be disabled completely for all clients in upcoming versions to avoid recursive Macro/Action looping infinitely. Therefore, it is best practice to avoid using this type of behavior in applications if they are to be future proof.