Any ETA for fixing the NCM 7.0 add Node functionality ?
The remark is quite confusing, is it a known bug related to the CRUD operations themselves, and Direct DB is possible, or are both not to be used ?
With NCM 7.0 not including the possibility to create an "Import from NCM" scheduled job anymore, it is unclear whats currently the right approach for creating a node both in NPM 10.1 and NCM 7.0 programatically...
Keep up the great work on the SDK, this is really a nice enhancement to your line of products !
Cheers
I can't give you an ETA, but I can tell you that we are looking at options to get that sorted out sooner rather than later. I will be sure to post in this forum when we have something for you.
Thanks Tim.
Can you advise on a possible workaround in the meantime ? Is it still possible to do a Direct DB insert or is it discouraged currently ?
Direct database insert might work, but we don't have instructions for it and it isn't something we can support. Unfortunately, I don't have another workaround to give you.
NCM 7.0.2 now provides a programmatic way to add a node. You can follow the instructions in the SDK to add a new node to the system, then invoke a new verb to add this node to NCM.
The new verb is Cirrus.Nodes.AddNodeToNCM, and it takes one argument: the NodeID. From PowerShell, it would look like this:
Invoke-SwisVerb $swis Cirrus.Nodes AddNodeToNCM 5
Mschenck,
Tdanner was eluding to a script now available and described How to automate the creation of Orion Platform (aka Core) nodes from the API.
Thanks to him (and Tomas) for their contribution to this.
