Skip to main content

What is the Difference between $PSItem and $PSItem.Something?

Diversity is a wonderful thing.  So many different experiences leads us to look at the same thing in so many different ways.  I just had a simple, yet really good question in my PowerShell class.
“What is the difference between $PSItem and $PSItem.something?”

Good question.  We are currently studying the PowerShell Pipeline.  As a result, we are looking at $_ and $PSItem.  These two automatic variables represent the current object in the PowerShell pipeline.  If you look at the PowerShell help file About_Automatic_Variables you will see this:
    $_
       Same as $PSItem. Contains the current object in the pipeline object.
       You can use this variable in commands that perform an action on every
       object or on selected objects in a pipeline.

I tend to use $_ because it is shorter and most of my content needs to fit nicely in a book or in a blog post.  Let’s look at an object that we will place in the PowerShell pipeline.
PS Variable:\> Get-Date | Get-Member -MemberType Properties


   TypeName: System.DateTime

Name        MemberType     Definition                                                                 ----        ----------     ----------                                                               DisplayHint NoteProperty   DisplayHintType DisplayHint=DateTime                                     Date        Property       datetime Date {get;}                                                       Day         Property       int Day {get;}                                                           DayOfWeek   Property       System.DayOfWeek DayOfWeek {get;}                                         DayOfYear   Property       int DayOfYear {get;}                                                     Hour        Property       int Hour {get;}                                                           Kind        Property       System.DateTimeKind Kind {get;}                                           Millisecond Property       int Millisecond {get;}                                                   Minute      Property       int Minute {get;}                                                         Month       Property       int Month {get;}                                                         Second      Property       int Second {get;}                                                         Ticks       Property       long Ticks {get;}                                                         TimeOfDay   Property       timespan TimeOfDay {get;}                                                 Year        Property       int Year {get;}                                                           DateTime    ScriptProperty System.Object DateTime {get=if ((& { Set-StrictMode -Version 1; $this.DisplayHint }) -ieq  "Date")...    

This object has several members.  This first example will show you the results of using just $PSItem
PS C:\> Get-Date | ForEach-Object { $PSItem }

Tuesday, July 12, 2016 1:15:22 PM

This second example will show you the result of using $PSItem.DayOfYear
PS C:\> Get-Date | ForEach-Object { $PSItem.DayOfYear }
194

This third example involves a method of the object.
PS Variable:\> Get-Date | ForEach-Object { $PSItem.AddDays(10) }

Friday, July 22, 2016 2:59:56 PM

See the difference?  When you reference $PSItem, you are referencing the entire object.  When you add the name of a property or the name of a method of the object to $PSItem, you are asking for the value of that property or for that method to execute.



Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.