On our latest data load, the api returned the following occasional error message: running for too long

What does this mean?

I've been trying to establish Account Teams through SForce API 2.5 and have not been able to get things set up properly.

For Accounts and Users that already exist, I have gone through the 2-step process of:
  1) Updating accountShare table with Access Rights for Accounts / Opportunities
  2) Importing accountTeamMember to establish roles

This should work, but for some reason when I update the accountShare table the Row Cause goes to Manual instead of Team, and the Access Rights I set never carry over to the actual Team Members.

Does anyone have any pointers or things to look out for when setting up Teams through the API?

Thanks

 

 

How do I tell which fields are required by the API, and which fields are set as required by the administrator through the setup section on the www.salesforce.com site? I just ran a describe call, and I don't see it there.

I noticed that the describe call no longer contains layout information. I use the layout information such as section, column, location, tab sequence of a given field within an entity to determine layout of custom UI's that I create. Since I use this information, the user is able to manage the layout of the custom UI through the same layout tools that salesforce offers.

Please consider adding this information back into the describe call.

Message Edited by foulox on 11-25-2003 08:05 AM

Can I include more than one file in an sControl?

I attempted to use the query call to get all of the leads a client has, which was over 20K through the API using Axis, and I got an out of memory error in the AxisClient.invoke method. Has anyone else experienced this. What is the best way to download large amounts of data through the API?

Are these error codes considered errors with individual elements of a batch or the entire batch?

Ever since I saw the mention of 2.1 in this message board I've been working on migrating my 2.0 code to 2.1, now I have a couple of questions. 

The first is how will point releases be announced in the future?  I only found out about the 2.1 release because of a response that Dave wrote to a question.

The next question is code related.  My query call isn't working, I suspect I made a mistake with the mapEntry for my filter, if you could verify my suspicion that'll be great, but here's the other thing that concerns me: the faultcode is 1005, and the faultString value is "size of request is too large".  According to the documentation 1005 is "session id is required for non-login request".  I don't see "size of request is too large" mentioned in the api documentation.

Below is the soap messages:
<pre>::SOAP Request:::
<?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:Header>
  <ns1:commonRequest soapenv:mustUnderstand="0" xsi:type="ns1:headerStruct" xmlns:ns1="salesforce">
   <session_id xsi:type="xsd:string">yH2l5vCsmOkhKarOFTK39P9J0qI8M3K0yOjZ65KtkNPxWz.k1lOfC9sL7XIgOp1DMTgQvaHQ9S1.RZFDRUFYHPbtzKggVlhL</session_id>
   <version xsi:type="xsd:string">2.1</version>
  </ns1:commonRequest>
 </soapenv:Header>
 <soapenv:Body>
  <ns2:query soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="sfconnector:SalesforceConnector">
   <scope xsi:type="xsd:string">filter</scope>
   <type xsi:type="xsd:string">contact</type>
   <maxRows xsi:type="xsd:int">-1</maxRows>
   <select xsi:type="soapenc:Array" soapenc:arrayType="xsd:string[1]" xmlns:ns3="salesforce" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <item>id</item>
   </select>
   <filter xsi:type="soapenc:Array" soapenc:arrayType="ns4:mapEntry[][1]" xmlns:ns4="salesforce" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <item soapenc:arrayType="ns4:mapEntry[3]">
     <item>
      <key xsi:type="xsd:string">field</key>
      <value xsi:type="xsd:string">ownerID</value>
     </item>
     <item>
      <key xsi:type="xsd:string">value</key>
      <value xsi:type="xsd:string"></value>
     </item>
     <item>
      <key xsi:type="xsd:string">operator</key>
      <value xsi:type="xsd:string">not equals</value>
     </item>
    </item>
   </filter>
   <idList xsi:type="ns5:ArrayOfString" xsi:nil="true" xmlns:ns5="salesforce"/>
   <ifModifiedSince xsi:type="xsd:dateTime">1950-11-06T22:39:45.857Z</ifModifiedSince>
   <useCaseSafeIDs xsi:type="xsd:boolean">false</useCaseSafeIDs>
  </ns2:query>
 </soapenv:Body>
</soapenv:Envelope>

::SOAP Response:::
<?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/>
  <soap:Body>
    <soap:Fault>
      <faultcode>1005</faultcode>
      <faultstring>size of request is too large</faultstring>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>
</pre>

Part of our methodology for loading data, de-duping data etc., has been to do a Data Export through the Weekly Export Service located in My Setup -> Organization Profile. This time I took a careful look at the IDs that are returned and noticed that they are all 15 characters which should be fine, however the first 3 characters of the 15 character IDs that are retrieved match the entity type code. So I'm a bit concerned that these IDs are being truncated at the tail end, rather then the front end. Here's an example:

The user id from the Export Service is:
00530000000c0pF

While the matching 18 Character ID is:
00530000000c0pFAAQ

We have noticed the same thing through the reporting interface.

Is this a problem, or is my understanding of the difference between the 15 and 18 character ID's wrong?

It looks like it should be in task.description, but during my test, I'm only seeing cc: showing up in the description field of the task entity, and I don't see the body of my email message anywhere.

I got the following error when trying to call a describe call against a lead, please let me know how to get around this.

faultString: common.i18n.LabelNotFoundException: IniFile - val convertedAccount.name not found in section LeadEntity

I'm using apache axis, but I've done plenty of describe calls using the same classes, and have never received this error.

I noticed that the describe call no longer contains layout information. I use the layout information such as section, column, location, tab sequence of a given field within an entity to determine layout of custom UI's that I create. Since I use this information, the user is able to manage the layout of the custom UI through the same layout tools that salesforce offers.

Please consider adding this information back into the describe call.

Message Edited by foulox on 11-25-2003 08:05 AM

Hi,

I'm a new developer, so this might be a silly question. I have created a Web Integration Link which uses scontrol, which in turn call a Java Applet. The applet runs fine locally on my labtop, but it is not showing up on the site.
Here is my html code for my scontrol object:





where in place of xxx I have put my applet class file, and also tried {!Scontrol_URL}.

Can someone please help? Any suggestions would be greatly appreciated.

Han

I have a Web Integration Link in SalesForce that redirects to a page in my server. I want to login and get data from salesforce without ask the password again...using the login in salesforce.

It's possible? My language is c#

Can you help me...it's important!

 

 

 

I am attempting create/modifify a task using the sForce 2.0 Partner version.  I am having a difficult time understanding the sObject that is used in creation objects in your system.  I understand that an sObject array is neccessary, but not sure how the sObjects in that array are setup.  Any help would be greatly appreciated...  An example would be nice.

-- Glenn

Can I include more than one file in an sControl?

Hi,

In my Salesforce account, I setup some fields as "Required" in my "Lead Layout" but when I make a "describe" call, the response does not indicate that the fields are required (ie: the nullable element is NOT "false" for these fields)

On the Salesforce web site, the fields are in fact "Required" when I try to create a lead.

What am I missing?

Thanks
Shun,

I attempted to use the query call to get all of the leads a client has, which was over 20K through the API using Axis, and I got an out of memory error in the AxisClient.invoke method. Has anyone else experienced this. What is the best way to download large amounts of data through the API?

I wrote a small program to login and then do a sfdc.describe.  Everything works fine, and i can actually output the fields coming back.  However, when i move this code into a servlet( same exact code ) and the code is executed from a servlet, i get the following error:

org.apache.xmlrpc.XmlRpcException: user not valid

I also checked the error code and it is 1112 ( invalid login )

Why is it working when it's running as a standalone program but not working when i'm in a servlet?  Anyone else encounter this?

I'm using apache's XmlRpcClient class.

 

 

 

Ever since I saw the mention of 2.1 in this message board I've been working on migrating my 2.0 code to 2.1, now I have a couple of questions. 

The first is how will point releases be announced in the future?  I only found out about the 2.1 release because of a response that Dave wrote to a question.

The next question is code related.  My query call isn't working, I suspect I made a mistake with the mapEntry for my filter, if you could verify my suspicion that'll be great, but here's the other thing that concerns me: the faultcode is 1005, and the faultString value is "size of request is too large".  According to the documentation 1005 is "session id is required for non-login request".  I don't see "size of request is too large" mentioned in the api documentation.

Below is the soap messages:
<pre>::SOAP Request:::
<?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:Header>
  <ns1:commonRequest soapenv:mustUnderstand="0" xsi:type="ns1:headerStruct" xmlns:ns1="salesforce">
   <session_id xsi:type="xsd:string">yH2l5vCsmOkhKarOFTK39P9J0qI8M3K0yOjZ65KtkNPxWz.k1lOfC9sL7XIgOp1DMTgQvaHQ9S1.RZFDRUFYHPbtzKggVlhL</session_id>
   <version xsi:type="xsd:string">2.1</version>
  </ns1:commonRequest>
 </soapenv:Header>
 <soapenv:Body>
  <ns2:query soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="sfconnector:SalesforceConnector">
   <scope xsi:type="xsd:string">filter</scope>
   <type xsi:type="xsd:string">contact</type>
   <maxRows xsi:type="xsd:int">-1</maxRows>
   <select xsi:type="soapenc:Array" soapenc:arrayType="xsd:string[1]" xmlns:ns3="salesforce" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <item>id</item>
   </select>
   <filter xsi:type="soapenc:Array" soapenc:arrayType="ns4:mapEntry[][1]" xmlns:ns4="salesforce" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <item soapenc:arrayType="ns4:mapEntry[3]">
     <item>
      <key xsi:type="xsd:string">field</key>
      <value xsi:type="xsd:string">ownerID</value>
     </item>
     <item>
      <key xsi:type="xsd:string">value</key>
      <value xsi:type="xsd:string"></value>
     </item>
     <item>
      <key xsi:type="xsd:string">operator</key>
      <value xsi:type="xsd:string">not equals</value>
     </item>
    </item>
   </filter>
   <idList xsi:type="ns5:ArrayOfString" xsi:nil="true" xmlns:ns5="salesforce"/>
   <ifModifiedSince xsi:type="xsd:dateTime">1950-11-06T22:39:45.857Z</ifModifiedSince>
   <useCaseSafeIDs xsi:type="xsd:boolean">false</useCaseSafeIDs>
  </ns2:query>
 </soapenv:Body>
</soapenv:Envelope>

::SOAP Response:::
<?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/>
  <soap:Body>
    <soap:Fault>
      <faultcode>1005</faultcode>
      <faultstring>size of request is too large</faultstring>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>
</pre>

Hi,

I was unable to express myself more concise, sorry.

Does anyone know if there is a problem with the following soap envelope.
I am trying to do an insert call.
The session id removed for clarity.

<?xml version="1.1" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/1999/XMLSchema"
  xmlns:tns="salesforce"
  xmlns:SOAP-ENC="http://www.schemas.xmlsoap.org/soap/encoding">
 <soap:Header>
  <tns:headerStruct>
   <session_id xsi:type='xsd:string'> . . . </session_id>
   <version xsi:type='xsd:string'>2.0</version>
  </tns:headerStruct>
 </soap:Header>
 <s:Body>
  <m:insert xmlns:m='sfconnector:SalesforceConnector'>
   <type xsi:type='xsd:string'>account</type>
   <record xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="tns:mapEntry[1]">
    <value xsi:type='tns:mapEntry'>
     <key xsi:type='xsd:string'>name</key>
     <value xsi:type='xsd:string'>fredin akkountti 54321</value>
    </value>
   </record>
  </m:insert>
 </s:Body>
</s:Envelope>

Sending it gives a fault. Faultcode 1101, record field must be struct.

The next thing I tried was to use the format in the SOAP examples, that is

<?xml version="1.1" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/1999/XMLSchema"
  xmlns:SOAP-ENC="http://www.schemas.xmlsoap.org/soap/encoding">

 <soap:Header>
  <tns:headerStruct>
   <session_id xsi:type='xsd:string'> . . . </session_id>
   <version xsi:type='xsd:string'>2.0</version>
  </tns:headerStruct>
 </soap:Header>

 <s:Body>
  <q1:insert xmlns:q1="sfconnector:SalesforceConnector">
    <type xsi:type="xsd:string">account</type>
    <record href="#id1" />
  </q1:insert>
  <soapenc:Array id="id1" soapenc:arrayType="tns:mapEntry[1]">
    <Item href="#id2" />
  </soapenc:Array>
  <tns:mapEntry id="id2" xsi:type="tns:mapEntry">
    <key xsi:type="xsd:string">name</key>
    <value xsi:type="xsd:string">fredin akkountti 54321</value>
  </tns:mapEntry>
 </s:Body>
</s:Envelope>

the response is the same.

Does it make a difference if the parts of the record parameter are
included through reference?

Also, if the envelope below would be collapsed in to a structure with
no references, would it look like:

  <q1:insert xmlns:q1="sfconnector:SalesforceConnector">
    <type xsi:type="xsd:string">account</type>
    <record xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="tns:mapEntry[1]"/>
     <Item xsi:type="tns:mapEntry">
      <key xsi:type="xsd:string">name</key>
      <value xsi:type="xsd:string">fredin akkountti 54321</value>
     </Item>
    </record>
  </q1:insert>

If so, isn't it said in the WSDL that the name of the elements inside a Map is 'value'?

I was just wondering if this could have anything to do with the error on the struct.

<xsd:complexType name="map">
 <xsd:complexContent>
  <xsd:restriction base="SOAP-ENC:Array">
   <xsd:sequence>
    <xsd:element maxOccurs="unbounded" minOccurs="0" name="value"
                 type="tns:mapEntry"/>                  // ^^^^^^ NAME
   </xsd:sequence>
   <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="tns:mapEntry[]"/>
  </xsd:restriction>
 </xsd:complexContent>
</xsd:complexType>

And more. Doesn't a map traditionally map keys to values (as the complex type mapEntry is
defined in the WSDL)? However, e.g. the loginresponse has a map with three items: server_url,
session_id and user_id inside valueMap tags of type "map". (This isn't 'tns:map' map for the
map defined in the WSDL, is it?)

I hope I made my point..

thanks

 - Jussi

 

Since the release of API 2.0 previous code written and tested with API 1.9 is failing, even with the version argument set as 1.9.  Is API 1.9 unavailable following this latest release?

The error is that the response SOAPElement seems not to have a type attribute in response to either the query or describe requests.

Any pointers are very welcome...

 

Thanks,

Brian.

 

It looks like it should be in task.description, but during my test, I'm only seeing cc: showing up in the description field of the task entity, and I don't see the body of my email message anywhere.

I got the following error when trying to call a describe call against a lead, please let me know how to get around this.

faultString: common.i18n.LabelNotFoundException: IniFile - val convertedAccount.name not found in section LeadEntity

I'm using apache axis, but I've done plenty of describe calls using the same classes, and have never received this error.

I am trying to use describe to get layout information but I don't understand how to do it. I can get global and account but layout is elusive. Am I missing something in the docs?

regards,

Paul