Export array with different number of columns

Question

I’m trying to create a report in Powershell but running into a problem when trying to export. Basically I have a loop that is adding the data to an array, however when I go to export all the data isn’t exporting. I broke it out of the loop so I can show you what’s happening.

What I'm expecting:

+----------+-----------+--------+
| HostName | Platform  | 3rdCol |
+----------+-----------+--------+
|  Test1   | Platform1 |        |
|  Test2   | Platform2 | 3rdCol |
+----------+-----------+--------+

What I'm getting:

+----------+-----------+
| HostName | Platform  |
+----------+-----------+
|  Test1   | Platform1 |
|  Test2   | Platform2 |
+----------+-----------+

Powershell:

#Create report array
$report = @()

#New object for Test1
$stats = New-object PSCustomObject
#Hostname column for Test1
$stats | Add-Member -Name HostName -Value Test1 -Membertype NoteProperty
#Platform column for Test1
$stats | Add-Member -Name Platform -Value Platform1 -Membertype NoteProperty
#Add row to report
$report += $stats

#New object for Test2
$stats = New-object PSCustomObject
#Hostname column for Test2
$stats | Add-Member -Name HostName -Value Test2 -Membertype NoteProperty
#Platform column for Test2
$stats | Add-Member -Name Platform -Value Platform2 -Membertype NoteProperty
#3rd column for Test2
$stats | Add-Member -Name 3rdCol -Value 3rdCol -Membertype NoteProperty
#Add row to report
$report += $stats

#Export only has two columns instead of 3
$report | export-csv c:\temp\report.csv -notypeinformation

Export-Csv infers the column headers from the first object that is piped to it. Instead of only adding the 3rdCol property to some objects, add it to all objects (just set it to $null for objects that don't need it) — Mathias R. Jessen
– Mathias R. Jessen, Commented Feb 10, 2016 at 17:47
@MathiasR.Jessen that would work in this example, but in a loop I'm dynamically creating the columns and don't really know how many columns there will be. — ntalekt
– ntalekt, Commented Feb 10, 2016 at 17:51

TheMadTechnician · Accepted Answer · 2016-02-10 17:54:28Z

2

When PS outputs an array it looks at the first record to determine what columns are needed, so you need to make sure that your first record has all of the properties of any of the members in the array, even if the value is $null.

If you do not know what the properties will be you can get that programatically after the fact with something like:

$Props=$report | ForEach{$_.PSObject.Properties} | Select -Expand Name -Unique
$Props|Where{$_ -notin $Report[0].psobject.properties.name}|ForEach{Add-Member -InputObject $Report[0] -NotePropertyName $_ -NotePropertyValue $null}

edited Feb 10, 2016 at 17:54

answered Feb 10, 2016 at 17:51

TheMadTechnician

36.5k3 gold badges48 silver badges63 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

ntalekt Over a year ago

that would work in this example, but in a loop I'm dynamically creating the columns and don't really know how many columns there will be.

TheMadTechnician Over a year ago

Updated to take care of dynamic properties.

ntalekt Over a year ago

Thank you! Works perfectly.

Collectives™ on Stack Overflow

Export array with different number of columns

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related