Trying to pull data from Service now using WSDL

swe1
Kilo Explorer

I am trying to pull data from Service now into our EDW. I am using SSIS, I read about the performance issues and see there are other tools which would help replicate the tables. But for now when I am using SSIS's Web Service task and use 'get records' method, I do not see any records pulled. But when I do a csv on the same I see lots of records in the browser.

below is the wsdl I am using for incident

https://NAME.service-now.com/incident.do?WSDL

and when I run the same with ?CSV it shows me records.

I have output to an xml, there is no error when I run the package all I see is

<?xml version="1.0" encoding="UTF-16"?>

<Result>The result is null. Either the result is null or the Web method returns void.</Result>

Please suggest.

Thank you.

7 REPLIES 7

we have this on https://site.service-now.com/incident.do?SOAP


and a query like the following which returns the relvant record(s)


Of course, change the fields as needed and the encoded query



<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://www.service-now.com/incident">


  <soapenv:Header/>


  <soapenv:Body>


          <u:getRecords>


              <u_versiant_id>30818</u_versiant_id>


              <__order_by_desc>sys_updated_on</__order_by_desc>


              <__encoded_query>work_notesISNOTEMPTY^sys_updated_on>javascript:gs.dateGenerate('2014-08-12','10:00:00')^work_notes!=adding a new note (title) | adding a new note into Autotask. This is the description</__encoded_query>


          </u:getRecords>


  </soapenv:Body>


</soapenv:Envelope>



Julian yes I used SOAP UI and the wsdl works for GetRequest Method if I take the optional variables out. i.e., '?' out. But on SSIS I am not sure how I can do this. I am looking in to that now.


Not using SSIS I am not sure


One of our partners uses Autotask and one of their developers had to write a "proxy" query data from Autotask and push to Servicenow. Part of it was to look at the intermediate u_xxx_incident table to check he had not sent the update over.


Othertime is needs to look at the incident or request tables too.


It is messy



Then again I have fun when I send them a ticket.   If it is a new ticket it is OK, but if it is an update, I have to query their record first, retrieve all the information and then add this information into the SOAP message I finally send them.


Not to much of a problem via a Script Include, but again, messy for something that should be so easy.