<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Option to group software inventory by package]]></title><description><![CDATA[<p dir="auto">Hi on the software inventory tab at the container level, would it be possible to add an option to switch the grouping from node to package?  So instead of seeing a list of nodes that you expand to see the contained software packages, you could see a list of software packages that you expand to see the nodes that have that software on it?</p>
<p dir="auto">I also notice, that when you use the filter at the top of the tab, it seems inconsistent as to whether it will expand a node containing the software filtered for or not.  eg: typing 'edge' might expand some nodes but not others.</p>
<p dir="auto">Would it be possible to consistently expand all nodes that contain a filtered software?  Or maybe as another feature request, have an 'expand all' 'collapse all' toggle/button at the top right to open all nodes up?</p>
<p dir="auto">Cheers.</p>
]]></description><link>https://forum.netxms.org/topic/8151/option-to-group-software-inventory-by-package</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 04:21:23 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/8151.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 10 Apr 2025 04:28:38 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Option to group software inventory by package on Fri, 11 Apr 2025 01:44:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/filipp-sudanov" aria-label="Profile: filipp-sudanov">@<bdi>filipp-sudanov</bdi></a> said in <a href="/post/34329">Option to group software inventory by package</a>:</p>
<blockquote>
<p dir="auto">Grouping by software package looks cumbersome - e.g. some software packages tend to have version number in the name, e.g. jdk-17... and jdk-21..., could be desirable to join them somehow... So unless it's a sponsored development we don't have resources available to go into this.</p>
<p dir="auto">But, to mention, software package information is accessible from NXSL, so it might be that for some usecases you can just script something.</p>
</blockquote>
<p dir="auto">ah yes, I see that would complicate things a lot. fair point with NXSL.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/filipp-sudanov" aria-label="Profile: filipp-sudanov">@<bdi>filipp-sudanov</bdi></a> said in <a href="/post/34329">Option to group software inventory by package</a>:</p>
<blockquote>
<p dir="auto">For expansion - I've registered a ticked to add expand/collapse buttons: <a href="https://track.radensolutions.com/issue/NX-2745" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-2745</a></p>
</blockquote>
<p dir="auto">Thanks, that would basically remove the need for grouping by software (the idea was to click once to expand rather than hunting through all nodes clicking).   </p>
<p dir="auto">So if you 1) filter up the top then 2) expand all, you can then 3) quickly export without too much clicking on each node.</p>
]]></description><link>https://forum.netxms.org/post/34333</link><guid isPermaLink="true">https://forum.netxms.org/post/34333</guid><dc:creator><![CDATA[normalcy]]></dc:creator><pubDate>Fri, 11 Apr 2025 01:44:45 GMT</pubDate></item><item><title><![CDATA[Reply to Option to group software inventory by package on Thu, 10 Apr 2025 10:15:46 GMT]]></title><description><![CDATA[<p dir="auto">For expansion - I've registered a ticked to add expand/collapse buttons: <a href="https://track.radensolutions.com/issue/NX-2745" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-2745</a></p>
<p dir="auto">Grouping by software package looks cumbersome - e.g. some software packages tend to have version number in the name, e.g. jdk-17... and jdk-21..., could be desirable to join them somehow... So unless it's a sponsored development we don't have resources available to go into this.</p>
<p dir="auto">But, to mention, software package information is accessible from NXSL, so it might be that for some usecases you can just script something.</p>
]]></description><link>https://forum.netxms.org/post/34329</link><guid isPermaLink="true">https://forum.netxms.org/post/34329</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Thu, 10 Apr 2025 10:15:46 GMT</pubDate></item></channel></rss>