Trigger Stops Working, or Not Properly Fetches Updates When a Modification Is Applied to the Visual

[morteza]

Hi,

I made a few changes on my visual (edited the DAX measure and changed some filters applied via the filter pane), and re-published the report. I then found the visual value that is fetched by trigger remained constant while it supposed to get zero because of a time filter applied on the visual. Interestingly if the visual value gets a new value it reflects the trigger but when it goes zero that doesn't change. I then had to create a new trigger from scratch for my purpose and made the old one inactive. Is there any way to avoid deleting/inactivating the existing triggers for such cases that a modification is made on the visual?

Here is the history of my existing trigger that I couldn't trust anymore:

and this one is the same but with the newly built trigger after I made the changes on the visual which works as expected:

[ReidWalter]

Ok, thanks. I will keep it in my mind.

[morteza]

Thank you @jameshutton 
Yes, As you also mentioned, to make this clear for users, that would be nice if a notification or warning bar/icon would be appeared on such triggers in the list of objects on the Reflex design mode to let them notified it won't work anymore due to a change in the state of visual to which it's linked.

[jameshutton · Accepted solution]

Hi @morteza 

When you create an alert from a visual, Data Activator builds the alert logic based on the state of the visual at the time that you create the alert. If you subsequently modify the visual, this will have no effect on the alert logic. This is by design. I appreciate it isn't necessarily obvious that it would work this way though. We will have a think about how to make it clearer that this is how it works.