The other possibility is that the namespace can generate the structure.
$getRecords1=[Incidents]::GetRecords()
This might prevent the object from being wrapped by PowerShell.
New-WebServiceProxy as way for update information
Forum rules
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Re: New-WebServiceProxy as way for update information
Solved
$SNowWS_Incidents = New-WebServiceProxy -Uri $SN_Web -Credential $cred #don't define the namespace here
$type = $SNowWS_Incidents.GetType().Namespace
$records = new-object ($type + '.getRecords')
we cannot use namespace on New-WebServiceProxy because it is now allowed to execute twice times the code if you follow this definition.
thanks for your help
$SNowWS_Incidents = New-WebServiceProxy -Uri $SN_Web -Credential $cred #don't define the namespace here
$type = $SNowWS_Incidents.GetType().Namespace
$records = new-object ($type + '.getRecords')
we cannot use namespace on New-WebServiceProxy because it is now allowed to execute twice times the code if you follow this definition.
thanks for your help
Vini Vidi Installi
Re: New-WebServiceProxy as way for update information
I thought that the namespace looked odd. It is not normally used.
Yes a type would do it. The service does not want to be changed and it wants the names to be set correctly although I am guessing that it is a bug. You should be able too change the name
Yes a type would do it. The service does not want to be changed and it wants the names to be set correctly although I am guessing that it is a bug. You should be able too change the name