XML node passed to function

I'm working on a script that converts a specific format of XML file to a
CSV document. I'm getting stuck at a point where I pass an object of
type System.Xml.XmlElement to a function, but the function receives an
object of type System.Object[] instead. I've confirmed with debugging
that these types are, in fact, what are being passed and received. I
can't figure out why the variable gets changed to System.Object[] by the
time it gets into the function.

I've tried building other XML-parsing scripts that only deal with
passing XML variables to functions, and these scripts work correctly.
They do not change the object type before it enters the function.

Can someone look at this script and tell me why the GetHeaders function
thinks it's getting a $XMLnode variable of type System.Object[] instead
of System.Xml.XmlElement?


param ($InputXML = (throw "You must specify an input XML file."))

function GetHeaders ($XMLnode, $RecordType)
{
if ($XMLnode -is "System.Xml.XmlText")
{
Add-Content -Path $RecordType + "s.csv" -Value $XMLnode.get_Name()
}
else
{
foreach ($ChildNode in $XMLnode.get_ChildNodes())
{
GetHeaders($ChildNode, $RecordType)
}
}
}

function GetData ($XMLnode, $RecordType)
{
if ($XMLnode -is "System.Xml.XmlText")
{
Add-Content -Path $RecordType + "s.csv" -Value $XMLnode.get_InnerText()
}
else
{
foreach ($ChildNode in $XMLnode.get_ChildNodes())
{
GetHeaders($ChildNode, $RecordType)
}
}
}

[xml] $xml = Get-Content -Path $InputXML
$RequisitionCandidates = $xml.VisionDataExchange.ExportData.get_ChildNodes()
foreach ($RequisitionCandidate in $RequisitionCandidates)
{
GetHeaders($RequisitionCandidate.Candidate, "Candidate")
Add-Content -Path Candidates.csv -Value "`n"
GetData($RequisitionCandidate.Candidate, "Candidate")
Add-Content -Path Candidates.csv -Value "`n"
GetHeaders($RequisitionCandidate.Requisition, "Requisition")
Add-Content -Path Requisitions.csv -Value "`n"
GetData($RequisitionCandidate.Requisition, "Requisition")
Add-Content -Path Requisitions.csv -Value "`n"
}


--
David
Stardate 8525.2

On Jul 10, 4:21*pm, David Trimboli <trimb...@xxxxxx> wrote: Hi David,

This is a common source of confusion in powershell. .NET methods use
brackets and comma separated arguments, but powershell functions do
not. Case in point:
a: 1 ; b: 2 a: 1 2 ; b:

As you can see, $a is object[] with two elements: 1 & 2.

So, in short you should space separate your function arguments.

- Oisin
PowerShell MVP
http://www.nivot.org/

Oisin (x0n) Grehan [MVP] wrote: Oh, god. I knew that. Argh! (I mean, arg!)

Thanks, Oisin.

--
David
Stardate 8527.1

Hehe, this still happens to me even today Having IDE that will have
special highlight whenever you use () with functions would save me lot of
time

Martin


"David Trimboli" <trimboli@xxxxxx> wrote in message
news:ea9mmi14IHA.4272@xxxxxx

Martin Zugec wrote:
I think from now on I'm going to name my functions just like cmdlets so
that I treat them the same way...

--
David
Stardate 8538.2