Behaviour of setOrUpdateTechNodeAttributeByName
Posted: 02 Dec 2011, 21:27
Hi
within standardFunctions the function setOrUpdateTechNodeAttributeByName creates a new instance of an attribute name value pair if there is no instance of the named attribute on the specified Technology_Node, even if there is already an existing instance of that specific Attribute_Value. The result of this approach is that you end up with many duplicate attribute_value instances, as every machine with "Number of CPUs = 1" creates a net new instance of that name value pair, rather than using the instance that the very first node created.
I understand that this makes editing the attribute value through the UI more intuitive on an individual node, but it makes reporting based on all nodes having the same value more challenging. Any thoughts?
Kevin
within standardFunctions the function setOrUpdateTechNodeAttributeByName creates a new instance of an attribute name value pair if there is no instance of the named attribute on the specified Technology_Node, even if there is already an existing instance of that specific Attribute_Value. The result of this approach is that you end up with many duplicate attribute_value instances, as every machine with "Number of CPUs = 1" creates a net new instance of that name value pair, rather than using the instance that the very first node created.
I understand that this makes editing the attribute value through the UI more intuitive on an individual node, but it makes reporting based on all nodes having the same value more challenging. Any thoughts?
Kevin