i believe you would use the oLines property of your $oAPInv object handle since you are executing this externally.

But $oAPInv.oLines is $NULL. Do you have an idea how I would do that?

Your oAPInv object's class is AP_Invoice_Bus not AP_Invoice_Svc, correct?

Have you check nLines?

Yes, I am using the BUS object. The nLines doesn't work either. But I looked into the Dispatch Object for C# and got some help on StackOverflow. Here is how I can access the Lines in PowerShell:

$m_flgGetProperty = [System.Reflection.BindingFlags]::Public + [System.Reflection.BindingFlags]::Static + [System.Reflection.BindingFlags]::IgnoreCase + [System.Reflection.BindingFlags]::GetProperty
$oAPInvLines = $oAPInv.GetType().InvokeMember("oLines", $m_flgGetProperty, $null, $oAPInv, $null)

Thanks for your help!

Glad you got it figured out. I don't see powershell used very often with BOI, think I have only seen one or two other posts on here and I recall one of them had really peculiar behavior with the GetValue method.

If you feel like reading, here's the link.

www.sagecity.com/.../384726

Thanks David. That was actually my question as well ;-). Not many people seem to use Powershell to interact with Sage 100. I am transitioning away from VBScript for these smaller project. Powershell has a much bigger toolbox, and it seems to be much faster when interacting with Sage then VBScript is.

Realized it was your question after linking to it.

VBScript is probably primarily used because it is used by sage 100 scripting events within sage 100 so it is easier to keep everything using the same language vs one language for internal scripts and another language for external scripts.