We definitely understand the desire, but it’s not like we can just “add it back in to CSV”. We need a completely different CSV mechanism.
Each tag supports N number of alarms, each alarm has X properties (core properties which change based on mode, extended properties based on which modules are installed, and “additional data” properties arbitrarily defined by the user). Anybody, feel free to propose a csv format that accommodates that.
The way it would probably work would be to have an almost “stack” based approach to the file:
#tag#, name, type, etc...
##, 'mytag', int, ...
#alarm#, name, mode, setpointA, customprop1, customprop2
##, 'Alarm1', 'NotEqual', 0, 'test', 'blah'
##, 'Alarm2', 'Equal', 1, 'test', 'blah'
At any particular point, only the properties defined in the type def ("#alarm#") would be set, and then the object would belong to the item above it.
Does that help anyone? It’s still not at all friendly for excel, but I guess it’s easier to look at than XML, which everyone seems to hate.
Regards,