Forum Discussion

XCT's avatar
XCT
Resolver I
2 years ago
Solved

Problem with Reflex (Data Activator): no triggering

Hi everyone,   I've set a reflex artefact from a card visual on a PBI report published in a PPC workspace. This KPI is a simple countrows. The model semantic below the report is connected in Direct...
Need Help
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi XCT 

     

    Here are a few steps and considerations to help resolve the issue:

     

    1. Check the Reflex Configuration: Ensure that the reflex is correctly configured to monitor changes as expected. Remember, after creating a reflex, you need to populate it with your data and ensure it's correctly monitoring for conditions. For more information on setting up reflexes, refer to the Get started using Data Activator - Microsoft Fabric | Microsoft Learn.

    2. Verify the Trigger Conditions: Review the conditions set for triggering the action. It's crucial that the conditions accurately reflect the changes you expect to detect in your KPI. For more details on creating triggers in design mode, see Teams activity - Microsoft Fabric | Microsoft Learn.

     

     

     

     

     

    Best Regards,

    Jayleny

     

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

     

     

     

  • jameshutton's avatar
    jameshutton
    2 years ago

    XCT , sorry for the late reply. The reason your trigger is only firing once during that range is that your condition is set to "becomes greater than zero". This means that the trigger will fire only when the value was greater than zero at time t, then becomes greater than zero at time t+1. If you want the trigger to fire continuously while your value is greater than zero, then you can do this by changing your trigger condition to "is greater than zero."

jameshutton's avatar
jameshutton
Community Admin
2 years ago

XCT , sorry for the late reply. The reason your trigger is only firing once during that range is that your condition is set to "becomes greater than zero". This means that the trigger will fire only when the value was greater than zero at time t, then becomes greater than zero at time t+1. If you want the trigger to fire continuously while your value is greater than zero, then you can do this by changing your trigger condition to "is greater than zero."