Comments
-
Thanks for the detailed reply, the issue does seem like an oversight in the v3 endpoint. I have quite a bit of code using the XML format and JOINs for queries, for now have switched to using RAW XML output for affected queries and changed the parsing around as needed. The REST/JSON endpoint does seem better and will…
-
Thank you!
-
Thanks that seems to have solved the issue, although we have other actions like Remanage/Unmanage node that still seem to work fine on the v2 endpoint. We should probably move to REST in any case.
-
Hello Tony, I have tried many different queries and they all seem to fail with XML AUTO if there are selects from multiple tables. I uncovered this behaviour when moving some code to the v3 service, running against the v1 or v2 services seems fine and returns properly defined XML. I have only seen this error mentioned on…
-
Yes that seems to be it.. although that requires the action to log the alert to the event log. Is that correct? Also there does not seem to be a way to get the alert for the event.. nothing links them together.
-
We are connecting to https://sw_url:17778/SolarWinds/InformationService?wsdl, if it helps I can attach the WSDL here. How can I tell what version of SWIS I am targeting? I know that v3 is installed on the SW instance but don't know what the SOAP call is actually using.