function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Tom.ax53Tom.ax53 

API 3.0 Problem

Hi All,

I read on the sforce.com website that all API 2.5 code is compatible with version 3.0 of the API. I have just updated my WDSL to version 3.0 and get a lot of bugs in my application now.

For instance, I can no longer create a mapEntry, the insert() method is no longer there etc...

I really really need some advice.

Thanks in advance!

DevAngelDevAngel

Hi Tom,

You have just upgraded your code from 2.0 to 3.0.  mapEntries and insert calls went the way of the dinosaur in November.  I submit that you will prefer the 3.0 to the 2.0, even though you have a bit of recoding to do.
Tom.ax53Tom.ax53

Yeah you're right. I've noticed that we were still on version 2.0 after making my post.

is there a good alternative for mapEntry in version 3?

Thanks !
Tarak SilliniTarak Sillini

Hi Dave,

Should code writen with api version 2.0 continue to work? we have a lot of code on version 2.0 and it all stoped working after the upgrade. I hope i do not have to rewrite everything.

 

Tarak Sillini
Kaydara Inc.
DevAngelDevAngel

Hi Tarak,

Would you mind posting details on the things that you were doing with 2.0 that are no longer working?  This is critical information for us, as we can't predict every use case that may be affected.

Thanks.
DevAngelDevAngel

Hi Tom,

The evolution from 2.0 to 2.5 was a big step requiring recoding of client apps to use 2.5.  The interface is much simplified in 2.5/3.0 and the mapEntry is no longer needed.  Please see the 3.0 samples to get an idea of the different approach in 3.0 versus 2.0.

 
Tarak SilliniTarak Sillini

Hi Dave, here is a specific call that fails. it sits there for 100 seconds and it throw a time-out

 

<?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="h_id1">

    <session_id xsi:type="xsd:string">eFfPbuFcdRb.Kb.fGy6wSBjyWFWQ3BvcJn20jBq0va_yQXPBkOlP381babGwHMVFR86M0WkjS6Hd_S1xjYg8yPbtzKggVlhL</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:insert xmlns:q1="sfconnector:SalesforceConnector">

   <type xsi:type="xsd:string">case</type>

   <record href="#id1" />

   <autoAssign xsi:type="xsd:boolean">true</autoAssign>

  </q1:insert>

  <soapenc:Array id="id1" soapenc:arrayType="tns:mapEntry[5]">

   <Item href="#id2" />

   <Item href="#id3" />

   <Item href="#id4" />

   <Item href="#id5" />

   <Item href="#id6" />

  </soapenc:Array>

 

  <tns:mapEntry id="id2" xsi:type="tns:mapEntry">

   <key xsi:type="xsd:string">email</key>

   <value xsi:type="xsd:string">skwok@hypnotix.com</value>

  </tns:mapEntry>

  <tns:mapEntry id="id3" xsi:type="tns:mapEntry">

   <key xsi:type="xsd:string">name</key>

   <value xsi:type="xsd:string">Sam Kwok</value>

  </tns:mapEntry>

  <tns:mapEntry id="id4" xsi:type="tns:mapEntry">

   <key xsi:type="xsd:string">subject</key>

   <value xsi:type="xsd:string">ATTN: Dave Abiteol .. Character with Props</value>

  </tns:mapEntry>

  <tns:mapEntry id="id5" xsi:type="tns:mapEntry">

   <key xsi:type="xsd:string">origin</key>

   <value xsi:type="xsd:string">Email - Kaydara Support</value>

  </tns:mapEntry>

  <tns:mapEntry id="id6" xsi:type="tns:mapEntry">

   <key xsi:type="xsd:string">ownerID</key>

   <value xsi:type="xsd:string">00500000003zPzy</value>

  </tns:mapEntry>

 </soap:Body>

</soap:Envelope>
DevAngelDevAngel

Hi Tarak,

I'll scrape up some of my old 2.0 code and see if I can clear the air.  Give me a day or two.  Thanks.