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.

Can't use custom variable in Dynamic Collection for SP / Release

Hello, I created a Dynamic Collection in PDQ Inventory to show which computers aren't running W10 v1809 yet by using a Custom Variable. Unfortunately the value field for SP / Release only accepts number input:

screenshot of dynamic collection problem

Is this by design? It looks like O/S Version does allow for a variable so maybe I'll use that instead?



Date Votes
  • Thank you for reporting this. I have confirmed that it is not currently possible to use variables in number fields. I have submitted an internal bug ticket. I have no ETA on when/if this will be changed.

  • Thanks Colby!

  • It would be useful to make a collection for Win10 releases in or not in service (support), for example SP / Release Is Less Than "1803" - as that changes every six months or so, when MS ships a new feature release or the old one gets to be 18 months old (30 months for the long term servicing releases for Enterprise & Education customers).

    It's not technically more difficult to do a collection using the OS version number, but you'd have to find out what the last build number was for the release before it was de-supported.

    If you really smart guys can't allow variables for numeric fields generally, how about some kind of special case in the application for marking serviced/supported OS versions, or just change SP / Release to a text field?

  • this is more of an issue now than before, as Windows is now on version 20H2.  Which cannot be set as the value since numerical is the only option.


  • 20H2 is 2009 in a numerical value.

  • I have made my own collections for supported and unsupported versions using the info at

    Windows 10 - release information | Microsoft Docs

    using a custom variable for the oldest supported build. It would be nice for everyone if there was something in the collection library to save all the duplication of effort.

  • You only need the first 3 digits of O/S Version when mapping to a Windows 10 build number.