Update soap message function error

[geet]

Hi All,

I am using update soap function to update incidents from source to destination but i am getting the below error message while testing it.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>com.glide.processors.soap.SOAPProcessingException: Web service update called without a sys_id, ignored</faultstring><detail>com.glide.processors.soap.SOAPProcessingException: Web service update called without a sys_id, ignored</detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Kindly help me in resolving it.

Regards,

Shikha Khanna

[Ankur Bawiskar · Accepted solution]

Hi Shikha,

Did you try insert function for updating. Generally insert function is preferred to insert/update information.

When the incident number matches it will update the info and if not found it will create a new incident. This holds true when your coalesce field is incident number.

Just try using insert function and also verify the syd ids

Mark Correct if this solves your issue or hit Like and Helpful if you find my response worthy based on the impact.

Thanks

Ankur

[geet]

Hi Ankur,

i tried the way you suggested but there is still some issue.

[geet]

Hi Ankur,

There was a mistake in my BR and the functionality that you have suggested is working.

But this is one-directional integration. what if i create an incident in A instance and it gets created in B now B update it and it get updated in A itself.

So, for this do i need to do the same things that i did for one way that means this time creating a WSDL in A and then SOAP message in B.

Regards,

Shikha Khanna

[JC Moller]

Hi,

When you update ticket on instance B, what value are you setting in the SOAP message to be used as the coalesce value on instance A for updating the original ticket?

To me it looks like you are sending current.number on Instance B. Are you also sending the original ticket id you received from instance A, when it was created on instance B? How are you maintaining these separate ticket id values in your workflow?

- Jan

[geet]

Hi Jan,

The steps that i have pasted in the above chat i have done the vice-versa of that from B to A and it is successful now.

Yes, i was sending the hardcoded value in my BR which was wrong as i forgot to remove the ' '. after removing it, it started updating the values in the incident.

Summary:

1.Created a WSDL in destination(instance B) in which i created a transform map and marked the number field coalesce to true..

2.Shared the WSDL to source(instance A).

3.Created an insert SOAP function on Source(instance A) and a BR to populate values in incident.

4.Created a WSDL in source(instance A) in which i created a transform map and marked the number field coalesce to true..

5.Shared the WSDL to destination(instance B).

6.Created an insert SOAP function on destination(instance B). and a BR to populate values in incident.

Now i am able to insert as well as update through both the instances.

Please guide if i have written something wrong or have missed something.

Regards,

Shikha Khanna