<![CDATA[Source node override in template or with NXSL/custom attribute]]>See here Source node override with templates (netxms.org)

With the new Collector object class I think this will be even more useful.

]]>https://forum.netxms.org/topic/8029/source-node-override-in-template-or-with-nxsl-custom-attributeRSS for NodeFri, 13 Nov 2026 07:30:34 GMTSun, 22 Sep 2024 07:17:45 GMT60<![CDATA[Reply to Source node override in template or with NXSL/custom attribute on Fri, 11 Apr 2025 21:15:10 GMT]]>There's still no easy way. Theoretically there could be an option to set source node from nxsl (and may be some hook script to set this right when template is applied). And there are many other things which can not be done from nxsl, so there's a lot of work to improve that.

So yes, it's possible to configure Script DCIs and do data collection that way.

Or another possible workaround is to have nxshell script that is executed as server's action and that script would change source node.

]]>https://forum.netxms.org/post/34344https://forum.netxms.org/post/34344Fri, 11 Apr 2025 21:15:10 GMT