0

I have a SOAP client which connects with Salesforce and do CRUD operations. Earlier I used to use Axis to generate stub and in that case it works perfectly but then I replaced axis with force-wsc due to some security vulnerabilities with axis. Here when I'm trying to update a date/datetime field it shows "INVALID_TYPE_ON_FIELD_IN_RECORD". Below are the two soap envelope created by axis(1st) and force-wsc(2nd) . Please let me know how can I resolve this issue.

axis generated soap envelope

wsc generated soap envelope

  • Try to remove 'T' from the datetime, like: 2019-06-19 07:00:45 – Mariia Illarionova Jun 19 at 7:01
  • And erase your session token from the screenshots or at least kill current session, because it's security vulnerability. – Mariia Illarionova Jun 19 at 7:02
  • Sure @MariiaIllarionova . I will kill the current session . Removing 'T' is not a option for us as we have developed a large solution where it is being used like this and changing it requires a lot of effort . I will try to use it by removing it to see if that works at least. – Dipankar Dey Jun 19 at 9:06
  • The explicit xsi:type="xsd:string"on EmailBouncedDate seems the likely cause of the problem. Try sending the same SOAP request with something like SOAPUI, but exclude that attribute. – Daniel Ballinger Jun 20 at 0:00
  • Yup, it is working that way . But now the question is , how can we specify this to force-wsc while it generates the envelope ? – Dipankar Dey Jun 20 at 7:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.