Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Dynamic Collection Filters Question

I have an inventory that contains a specific software, in this case Thunderbird, that is also the current version.  So I make a collection that has 2 filters:

  • Application   Name    Contains                             Thunderbird
  • Application   Version  Version Not Lower Than    102.0.2

You can see a screenshot of this below.

Here's what I don't understand.  Does the second filter for the version only look at the Application Version for the Thunderbird?  Or does it look for ANY application that may have the version 102.0.2?  It would be a pretty big coincidence to have 2 unrelated pieces of software have the same version number, but it could happen.

Are the 2 application filters linked or unrelated?


PS  This collection works properly, I think.  But only because no other software has the same Version number.




Date Votes
  • I try to look at filters like Boolean Legos. "ALL of the lines contained within this group filter must be TRUE for a computer to appear in this collection."

    "Does this computer have an application whose name contains 'Thunderbird' AND whose version is not lower than 102.0.2?"

  • David,

    I think this is what you want instead:



    ------Application / Name / Contains / Thunderbird

    ------Application / Version / Version Not Lower Than / 102.0.2

  • My collection is working properly.  I'm just trying to understand how collection filters work. 

    Also, I think your version is the same as mine.  I don't think you need the extra Any.


  • David,

    I always structure mine in that way in case I want to add additional applications later, e.g. show me all computers with Outlook over version 20 or Thunderbird over 102. In that case you would want those grouped under different "All" group filters, but you're correct that you don't technically need it for your collection. I find that it is more logical this way so I prefer to do it that way.

    If you want a more in-depth explanation of how it works under the hood I can't answer that unfortunately, maybe a PDQ employee could chime in and answer.

  • Your structure makes sense.