Filter PowerShell Output with the Out-Gridview Cmdlet

re: Filter PowerShell Output with the Out-Gridview Cmdlet

jrv — Wed, 01 May 2013 16:00:56 GMT

@szilard - issue is with PowerShell V2 and V3. Windows 8 has V3 and a newer and fancier grid. This article was written for V2 on Windows 7 or earlier which has the older grid.

No matter how I do this on V2 it sorts correctly. On V3 the column is now a string so it cannot be sorted correctly and it cannot be matched correctly and teh drop down will not show equla/greater/less because it is seen as NaN.

My answer was to use the select to get the real column and then you will have all numbers.

SO you are correct in what you posted. I posted to say that thisis handled differntly in QWIndos 8 and in all systems running V3 because the fields are now strings.

You can edit the formatter file and chhage this back to the V2 behavior and you might post it on 'connect' as a possible bug. Format files can be dynamically loaded as needed to specify alternate default behaviors for compatibility with older scripts. (Blog article needed here!)

re: Filter PowerShell Output with the Out-Gridview Cmdlet

szilard — Wed, 01 May 2013 14:42:12 GMT

@jrv,

so then, how do you produce the screenshot above:

blogs.technet.com/.../5684.HSG_2D00_2_2D00_25_2D00_11_2D00_06_5F00_thumb_5F00_7AC35438.jpg

re: Filter PowerShell Output with the Out-Gridview Cmdlet

jrv — Tue, 26 Mar 2013 21:13:07 GMT

@szillard

If you inspect all of the properties carefully you will see that all of the alias properties are strings. IF we do a select * we get only the numeric properties. Look at the headers.

With one we get header for WS "WS(K)" which I an alias that has been converted to (K) by the formatter. With the other we get just WS which is the original unconverted number.

To see how this is done look into the format files.

re: Filter PowerShell Output with the Out-Gridview Cmdlet

Szilard — Tue, 26 Mar 2013 20:40:44 GMT

It is not all lost:

if I do :

Get-Process | Select-Object -Property * | Out-GridView

or specify the properties one by one

instead of

Get-Process | Out-GridView

then everything works properly. All Integers are sorted as such.

I checked with other people running win 8, and it seems they can not reproduce the example in this article either. WS(K) is simply handled as a string (unless they use Select-object-property) and so it can be sorted alphabetically only, the "less than or equal" option is not available only options like "contains" and such.

re: Filter PowerShell Output with the Out-Gridview Cmdlet

Bokros — Fri, 22 Mar 2013 18:37:11 GMT

So could you explain me why Out-GridView sorts VM(M), WS(K), PM(K) and NPM(K) as if they were strings not int values?

When I sort them I don't want to see them in alphabetical order.

It absoluetly does not make sense to sort PM(K) as 1060, 107300, 1084,108432, 175, etc...

I would think it is also wrong that the example you mentioned plain fails, there is no " is less than or equal to" to the WS(K) criteria, only "equals", "does not equal" and some other string related criteria.

Is there some kind of configuration that enables Out-GridView to recognize integers? I mean in case it is not the Handles criteria, because for some reason the values of "Handles" is handled as integers. There must be a completely reasonable explanation for this. I can't wait to read it.

re: Filter PowerShell Output with the Out-Gridview Cmdlet

Szilard — Thu, 21 Mar 2013 16:49:07 GMT

On my version less-than-or-equal and greater-than-or-equal is not an option any more, the options I see are the exact same as they are for the CPU(s) and other strings. It is like it handles the values as if they were strings not numbers. The default value is contains. And it is the same for each criteria.

re: Filter PowerShell Output with the Out-Gridview Cmdlet

Chris F — Sat, 26 Feb 2011 02:06:34 GMT

Anyway you can bottle this up and put it on Youtube ? This was hilarious and educational at the same time :) ...

Awesome...