function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
prudhviprudhvi 

select list not specified in query?

Hi,

 I wrote one java program to fetch an opportunity details using query method.(scope is idList).

It was worked well upto yesterday.  When I run the same program Today I am getting SOAP fault with

fault string  select list not specified in query.

Please let me know whether there  is  any change in the  API?  .

I am including my soap request at the end. Please look at the message and advise me if there is any change.

any help would be much appreciated.

Thanks and regards,

Prudhvi

 

 

I am using following soap request to fetch the opp details.

Request:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="salesforce" xmlns:types="salesforce/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Header>
    <tns:headerStruct id="id1">
      <session_id xsi:type="xsd:string">A88zC97HIqHnZIlRhIemUk5cNamuFFrgC8.mkYiGGVDEesUfciyliy._DWGd4UrmD1qjRrjmKArOo.rZcbQUIvbtzKggVlhL</session_id>
      <version xsi:type="xsd:string">2.0</version>
    </tns:headerStruct>
  </soap:Header>
  <soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <q1:query xmlns:q1="sfconnector:SalesforceConnector">
      <version xsi:type="xsd:string">2.0</version>
      <session_id xsi:type="xsd:string">A88zC97HIqHnZIlRhIemUk5cNamuFFrgC8.mkYiGGVDEesUfciyliy._DWGd4UrmD1qjRrjmKArOo.rZcbQUIvbtzKggVlhL</session_id>
      <scope xsi:type="xsd:string">idList</scope>
      <type xsi:type="xsd:string">opportunity</type>
      <maxRows xsi:type="xsd:int">1</maxRows>
      <select href="#id1"/>
      <idList href="#id2"/>
    </q1:query>
    <soapenc:Array id="id1" soapenc:arrayType="xsd:string[9]">
      <Item>id</Item>
      <Item>name</Item>
      <Item>accountID</Item>
      <Item>type</Item>
      <Item>leadSource</Item>
      <Item>amount</Item>
      <Item>closeDate</Item>
      <Item>stage</Item>
      <Item>probability</Item>
      <Item>description</Item>
      <Item>closed</Item>
      <Item>won</Item>
      <Item>createdDate</Item>
      <Item>createdByID</Item>
      <Item>lastModifiedDate</Item>
      <Item>lastModifiedByID</Item>
    </soapenc:Array>
    <soapenc:Array id="id2" soapenc:arrayType="xsd:string[1]">
      <Item>00600000006qJqB</Item>
    </soapenc:Array>
  </soap:Body>
</soap:Envelope>

 

Response

 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="salesforce" xmlns:types="salesforce/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema ">

<soap:Header/><soap:Body><soap:Fault><faultcode>ÑR</faultcode><faultstring>select list not specified in query</faultstring></soap:Fault></soap:Body></soap:Envelope>

DevAngelDevAngel

Hi prudhvi,

There has been a regression identified in the API as a result of a patch release last night.  We will have a fix out at some time today.  I will post to this thread when the problem is resolved.  As of now, it seems that the problem is only with the query using idList scope.  A work around is to use a query using filter scope using the id as the filter.

prudhviprudhvi

 

Hi Dave

  Hi prudhvi,

There has been a regression identified in the API as a result of a patch release last night.  We will have a fix out at some time today.  I will post to this thread when the problem is resolved.  As of now, it seems that the problem is only with the query using idList scope.  A work around is to use a query using filter scope using the id as the filter.

Dave
Developer Program Manager

prudhviprudhvi

 

Hi Dave

 Hi prudhvi,

There has been a regression identified in the API as a result of a patch release last night.  We will have a fix out at some time today.  I will post to this thread when the problem is resolved.  As of now, it seems that the problem is only with the query using idList scope.  A work around is to use a query using filter scope using the id as the filter.

Dave
Developer Program Manager

prudhviprudhvi

Hi Dave,

Thanks, I have tried with filter scope. Still I got the same error.

Thanks,

Prudhvi

 

ChristianChristian

Dave,

I have also received this same exception ("select list not specified in query") since last night (7/31 around 6:00 PM) calling the query method using filter scope.  This happens running my VB.NET code, as well as the sample code from this site.

In addition, I've been receiving a "record field is missing" exception on an update call that was previously working as well.  I just wanted to note this so the fix to the patch includes a resolution for this as well. Let me know if additional details are required.

Christian

Christian Aaselund

Acetta LLC

206 332 0440 x1008

206 719 8526 mobile

206 332 0604 fax

www.acetta.net

 

Message Edited by Christian on 08-01-2003 11:37 AM

DevAngelDevAngel

Hi Christian,

Thanks.  The problem seems to be a regression in parsing the structure of the selectList parameter and the record parameter in update and delete.  As I understand it, this is due to some changes that where made to fix some issues with Apache Axis generated messages.  We are dedicated to resolving this and will let everyone know when the problem have been fixed.

Thanks for you patience and input.

DevAngelDevAngel

The problems that where introduced late yesterday and early today have been repaired and the production servers have been updated.  As a result of this interuption in service, we are implementing additional checks and balances in the form of additional layers of regression testing and additional layers of compliance testing.

Rest assured that this type of outage will not happen again.  sforce is a division of salesforce.com and as such enjoys the benefits of the experience and expertise that has made salesforce.com such a big success. 

Thank you for your diligence in bringing the symptoms of the recent problem to our attention and providing timely input that allows us to provide timely support.

Message Edited by DevAngel on 08-06-2003 09:32 AM

prudhviprudhvi

Hi Dave

Today  I am getting this error again( select list not specified in query)

Please let me know when will it get fixed.

-Prudhvi

 

DevAngel2DevAngel2

Hi prudhvi,

There is no change in the API.  You code should work, your message is correct and well formed.  We have had a regression in a bug that was previously fixed.  We are working on an update to the service right now. 

pawanpawan
Yes me too.
prudhviprudhvi

 

Hi Dave,

I am still getting the same error.

Please inform us after the bug is fixed.

Thanks,

prudhvi

DevAngel2DevAngel2

Yup, will do.

Don't want to rush the fix.  We want to make sure that we don't unwittingly break something tangental to the problem.

pawanpawan
Is there a work around?
DevAngelDevAngel
The fix is in.  You should have full functionality back now.
prudhviprudhvi

Still I am getting same error message.

Can you please check that again

DevAngelDevAngel

Hi prudvhi,

What libraries are you using for SOAP?  I am not seeing any problems with Axis libraries, are you using something else?

ddatbigddatbig

Please fix this problem ASAP.

Also if possible suggest alternative SOAP query to get one single entity by id.

 

Thanks,

DD

DevAngelDevAngel

What exactly is the problem that you are having?  The selectList issue was resolved months ago.  We have numerous samples that demonstrate using the API in java including queries.  What is it that you reckon is broken?