+ Start a Discussion
laurentblaurentb 

small diff between v2.5 and v3.0

Hi,

I have a slight difference when I call search in v3.0 than in v2.5.

Id is return as an array with twice the same element.

Is it the normal behavior in v3.0 ?

I am running this query

select Id, Name from Account where Phone ='************'

with 2.5 I get

Array
(
    [0] => stdClass Object
        (
            [done] => true
            [queryLocator] => 
            [records] => stdClass Object
                (
                    [type] => Account
                    [Id] => 00130000001qpjkAAA
                    [Name] => ******                )

            [size] => 1
        )

)

with 3.0 I get

Array
(
    [0] => stdClass Object
        (
            [done] => true
            [queryLocator] => 
            [records] => stdClass Object
                (
                    [type] => Account
                    [Id] => Array
                        (
                            [0] => 00130000001qpjkAAA
                            [1] => 00130000001qpjkAAA
                        )

                    [Name] => *****                )

            [size] => 1
        )

)
here is the returned xml with v3.0
  xml version="1.0" encoding="UTF-8" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<queryResponse xmlns="urn:partner.soap.sforce.com">
<result>
  <done>truedone>
  <queryLocator xsi:nil="true" />
<records xsi:type="sf:sObject" xmlns:sf="urn:sobject.partner.soap.sforce.com">
  <sf:type>Accountsf:type>
  <sf:Id>00130000001qpjkAAAsf:Id>
  <sf:Id>00130000001qpjkAAAsf:Id>
  <sf:Name>****sf:Name>
  records>
  <size>1size>
  result>
  queryResponse>
  soapenv:Body>
  soapenv:Envelope>

Message Edited by laurentb on 04-12-2004 07:00 PM

Message Edited by laurentb on 04-12-2004 07:10 PM

Message Edited by laurentb on 04-12-2004 09:37 PM

rchoi21rchoi21

The partner WSDL defines four elements: a type, fieldsToNull, Id and the any. Because the sObject is defined as a sequence of these fields, they must appear in that order in the request and response.

The sObjects returned in the partner WSDL 3.0 properly reflect the WSDL. Previous version of the responses were slightly incorrect.