I have found an issue with Alarm Metrics. I have a folder of tags, and there is Alarm Metrics for this folder. When I open the Alarm Metrics I can see a lot of values about my active alarms for all the tags in the folder. That works fine.
Then I put a tag binding on a custom property in my page view (by which I mean it is the main view for a current navigation route) and the tag binding points to the path of the folder "Alarm Metrics.activeAckCount" . When I do that and I open the view either in the designer or in the browser session, then sometimes (it is like 50% of the time) it breaks the Alarm Metrics and they start showing Bad_NotFound. This is a big problem, because I rely on the Alarm Metrics to show active alarms.
For now I believe I have found a workaround, and that is to create an embedded view, put the Alarm Metrics bindings there, use that embedded view in my main view and delete all custom property tag bindings pointing to "Alarm Metrics.x" from my main view. That seems to work fine. But even just creating one custom property on the main view pointing to the folders "Alarm Metrics.x" will break it again (~50% of the time) and cause them to be Bad_NotFound.
Any ideas? Am I doing something wrong or is this a bug?
