Skip to main content

How to find if a property in a custom object has a NULL NoteProperty

This was a bit of a different problem.  How to find if a property in a custom object has a NULL value.  The client had a collection of objects that they gathered from their environment with PowerShell.  They needed a way to find out if any of the NoteProperties had a NULL value.  I created the function below.  You send it the collection of objects you are interested in probing for a NULL property value and it will return the index number of the object in the collection that has one.

 

Function Find-NullProperty

{

    [cmdletbinding(HelpUri="http://get-help-jason-yoder.blogspot.com/2012/10/find-nullproperty.html")]

    Param (

        [Parameter(Mandatory=$True)]$Object

    )

    # Check to see if an object has any NULL values in

    # its properties.

 

    # Create an object to output to the calling statement.

    $Output = @()

 

    # Index number to return for to denote the instance of an object

    # (should multiple instances be sent) that the Null value if found

    # in.

    $Index = -1

 

    # Extract the names of the properties of the object.

    $PropNames = (($Object | GM) |

      Where {$_.MemberType -eq "NoteProperty"} |

      Select-Object -Property Name).Name

 

    #Cycle through each object

    ForEach ($Obj in $Object)

    {

        # Increment the Index.

        $Index++

 

        # Set to $True is a $Null value

        #is found in a property.

        $NullFound = $False

 

        ForEach ($Prop in $PropNames)

        {     

            If ($Obj.$Prop -contains $Null)

            {

                $NullFound = $True

            }    

        }

        If ($NullFound)

        {

            # Create the object to be returned.

            $Obj = New-Object -TypeName PSObject

           

            # Add object members

            $Obj | Add-Member `

                    -MemberType NoteProperty `

                    -Name "Index" `

                    -Value $Index

           

            # Send the object to the output array.

            $Output += $Obj 

        }

    }

    Write-Output $Output

<#

.SYNOPSIS

Indicates if an object has a property that is $NULL

 

.DESCRIPTION

Search through a collection of custom objects and returns the index

number of any instance that has a $NULL value in a NoteProperty

 

.PARAMETER Object

The Object, or collection of objects that may contain a NULL value

in a note property.

 

.EXAMPLE

Find-NullProperty $Object

 

 Index

 -----

     1

     2

 

Returns the index number of instance of a collection of object in which

a NoteProperty has a NULL value.

 

.NOTES

Provided without warranty or support.

Author: Jason Yoder.

#>

}

 

Comments

Popular posts from this blog

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.