Is there a way to remove an XML element in a SOAP getRecord response?

[ctsmith]

Is there a way to remove an XML element in a SOAP getRecord response?   It's a field that's not needed and causing an issue in the response.   Can you write a BR on query that removes that element in a response?   Or maybe a setting at the table level on the field?

Thanks,

Chris

[Chuck Tomasi]

Hi Chris,

It's been a while since I've done a SOAP integration, but it sounds like re-downloading the WSDL is your way to go. It's the "definition" of what they can expect. If you've suddenly started injecting new elements in the XML, that could freak out the app. I'd start there.

[Chuck Tomasi]

Hi Chris,

Did the new WSDL fix the issue?

[ctsmith]

Probably.   They asked for it before I even posted this thread and I tried to head off a total rebuild to save some hours, but I think it tested successfully in their DEV system.   No QA testing or move to PROD yet.

Thanks!

[Ahmed Hmeid1]

Hi, I think you can create an ACL on the fields you don't want to send back to not allow access if it's not an interactive user (!gs.getSession().isInteractive()) or if you want to block it from a particular user, add that as a condition. Not particularly pretty though.

Axis can be very picky! It stores the WSDL definition and if the returned value doesn't adhere to it in anyway, it just falls over - I suppose that was one of the "nice" things about SOAP. It also can be hard to get it working with complex wsdls but I don't think the OOB web services use any complex WSDLs (could be wrong)

[ctsmith]

Oh, I like!   ACL would be a good trick to try.