Behaviour of setOrUpdateTechNodeAttributeByName

Post Reply
Kevin Campbell
Posts: 40
Joined: 13 Sep 2010, 20:26

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
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Kevin,

Thanks for pointing this out.
This is a function that goes back a few years and is probably a bit specific (being about attributes specifically for Technology Nodes). I agree that it would make more sense to re-use the required values rather than create unique instances for each Technology Node - even through the UI.

We've been making some updates (mainly to fix bugs) in the standardFunctions library recently, so we'll get this fixed too and upload the revised version.

Jonathan
Essential Project Team
Post Reply