Hello,
I have an interface that I'm building that is meant to allow authorized users to add / delete / configure alarms on tags.
Each of the label_value view instances (the view with the label and the numeric entry field / dropdown / text entry field) has a tag property as a "path" parameter in the following format:
[default]{area}/{machine}/{metric}/Alarms/{alarm name}
This "label_value" view encapsulates another view, which contains the label and the value. There is a "value" Input/Output parameter on this view, which represents the alarm property's value:
The binding on the "value" parameter is a bidirectional tag binding. It utilizes that path of the alarm (in the format previously specified).
The issue I'm experiencing is that writing to the "value" parameter does not write back to the tag alarm property as expected. Is this a known issue? Can bidirectional tag bindings not be used to write to individual tag properties besides the tag's value?
The value changes momentarily when I modify the value in the input field of the label_value view, but it quickly changes back to whatever the tag alarm property is. Changes to the input field do not appear in the tag properties when monitoring from the tag browser.
I'm aware that I could use system.tag.configure() to achieve the same result, but I'd like for this to work using a bidirectional tag binding, if possible.
EDIT:
I noticed that my designer wasn't in read/write mode. After switching to read/write mode and attempting to change a tag property via my view, I received the following error:
I'm assuming that this means that I can't modify tag properties with a bidirectional tag binding.
Thanks in advance for any help.