Nate Bergey
My feedback
-
67 votes
An error occurred while saving the comment An error occurred while saving the comment Nate Bergey
commented
This would be awesome, so it's obvious when the tag naming deviates from the template. Please implement!
Nate Bergey
supported this idea
·
Stephen, yes I understand the need and benefit of being able to deviate from the template, the point is highlighting when the attribute configuration deviates from the template. With your example, I would design the template such that attribute(s) in the motor template can be used to store variables used in the substitution string for the tag path. This way the configuration of the voltage measurement attribute is the exact same across all motors, even though the tag name is different (with tag Motor-12:Voltage, I'd store the Motor-12 in an attribute 'AssetId' with a value manually entered as Motor-12). In general, I'd consider deviations from the template as areas where the template/tags can be improved for better standardization, making it important that these deviations are visible to the users, instead of hiding it until a user reset the element to the template which will break any changes made.