Skip Navigation
Expand
Custom fields not returned in SOAP response
Answer ID 12437   |   Last Review Date 12/23/2022

Why are all fields, including custom fields/custom objects, from the B2C record not shown after doing a "GET" SOAP operation?
 

Environment:
Connect Web Services for SOAP (CWS) API
Version 1.4
 
Resolution:
When you are using a SOAP GET request to pull all fields including custom fields from a core object, such as Incident, your SOAP request can be built a couple of different ways;
  1. Specify a Custom Fields tab in your SOAP request:  <ns4:CustomFields/>.  This will pull all of the custom fields from the table specified in your SOAP envelope.  See example below of using the <ns4:CustomFields/> tag in a SOAP envelope for a specific incident;
<soapenv:Body>
        <ns7:Get xmlns:ns7="urn:messages.ws.rightnow.com/v1_4">
                        <ns7:RNObjects xmlns:ns4="urn:objects.ws.rightnow.com/v1_4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns4:Incident">
                             <ID xmlns="urn:base.ws.rightnow.com/v1_4" id="2252" />
                        <ns4:CustomFields/>     
                    </ns7:RNObjects>    
            </ns7:Get>
    </soapenv:Body>
</soapenv:Envelope>
 
     2. Use GenericObject in the SOAP GET envelope.  See Get with Generic Objects Documentation for an example.
 
 
For the entire Connect Web Services for SOAP API documentation, refer to Answer ID 5169: Technical Documentation and Sample Code.