In a driver we have been using for a long time, we are executing the below method to rename an element.
However when using this in DMA version 10.3.1.0-12509 we noticed the element does not get renamed, but recreated with empty configuration leaving it in a corrupt state.
Do you have any alternative methods to accomplish the rename without changing the existing configuration?
string sEditElementString = sNewName + “| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | “;
object oResult = protocol.NotifyDataMinerQueued(160, new object[] { sCurrentName, Convert.ToInt32(protocol.DataMinerID) }, sEditElementString);
Hi Mieke
In PTP we use this code, maybe this can be of help? Do note, this is to update your own element (hence the async).
// Needs to happen async as it will cause RTEs otherwise
AddElementMessage updateName = new AddElementMessage
{
DataMinerID = protocol.DataMinerID,
ElementName = newElementName,
ElementID = protocol.ElementID
};protocol.SLNet.RawConnection.Async.Launch(updateName);
Note that this is an internal call and we do not recommend using this, as it is not officially supported and we cannot guarantee that it will still work in the future. As a rule, you should avoid using SLNet calls, as these are subject to change without notice. We recommend to instead always use the correct UI or automation options provided in DataMiner Automation or through our web API.
As a note: the reason of the corruption was due to using the local DataMinerID via protocol.DataMinerID instead of the DataMinerID of the existing element.
Due to the size of the system, elements are now created on other agents in the cluster.