With Winter '16 starting to appear on Sandboxes I've started encountering problems with the Partner SOAP API.

The initial problem is around the new soapType enumeration values. In particular <enumeration value="urn:SearchLayoutFieldsDisplayed" />.

This soapType comes back from a call to describeSObjects with the sObjectType of "SearchLayout" for the "Fields Displayed" field.

Making the call against API v34.0 returns a field with this soapType. This in turn causes problems for the, in my case, .NET code that processes the SOAP XML response into strongly typed objects. This soapType isn't known or valid in v34.0 and results in an error:

System.InvalidOperationException: There is an error in XML document (1, 2239646). --->
System.InvalidOperationException: Instance validation error: 'urn:SearchLayoutFieldsDisplayed' is not a valid value for soapType.

Rolling forward to v35.0 of the Partner SOAP WSDL resolves the problem, but restricts the code to calling orgs that have been upgraded to Winter '16.

Should using v34.0 of the Partner API only return results that can be handled by the corresponding WSDL?

Edit - Raised as support case 12544039

  • 1
    I am using soap api 33.0, with winter 16 i am getting the following exception org.apache.axis2.databinding.ADBException: Unsupported type urn:partner.soap.sforce.com VisualforcePage does anybody have any idea on this ? Sep 28, 2015 at 9:10
  • @KarunKumar I'd suggest asking a new question about your specific problem. Include a SOAP call you are making if possible (which method are you calling). Note that the complexType "VisualforcePage" was added in v35.0 of the Partner WSDL. Sep 28, 2015 at 18:44
  • @KarunKumar Feel free to link to the new question from the comments here. If need be I can help with raising a support case. Sep 28, 2015 at 18:47
  • Thanks @Daniel Ballinger. I have posted a new question. below is the link salesforce.stackexchange.com/questions/94205/… how can i raise support case ? Sep 29, 2015 at 19:18
  • I'll look into it. Please post this as a comment rather than an answer to the question above. You might need to earn a bit more reputation before this option becomes available to you. Sep 29, 2015 at 19:27

1 Answer 1


Sounds like a bug, you are correct that old API versions shouldn't start returning enumeration values added in later API versions.

Response from support for case #12544039

R&D has set the bug corresponding to the issue - "New enumeration value of SearchLayoutFieldsDisplayed is returned in old api version, breaks old api clients" with the highest priority and the bug is scheduled for a fix on our next patch release ( 10/06[/15] ). After that patch fix, this issue shouldn't exist anymore.

  • Thanks. Will see what comes of my support case. Mostly published the question as a public service announcement in case others encounter it. Sep 24, 2015 at 3:03
  • 1
    Sorry you're having trouble, i passed this on to the API team to look at.
    – superfell
    Sep 24, 2015 at 3:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .