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
kpichakpicha 

INVALID_TYPE received when doing a create

here is the soap message that I sent:

 

<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:SessionHeader soapenv:mustUnderstand="0" xmlns:ns1="SoapService">
   <ns2:sessionId xmlns:ns2="urn:enterprise.soap.sforce.com">0kGvdc1oBLNSNwZYAad2z9KdIs_lIgFRIzhnzK6Tp.a2s5ZHXqHEkbo.fAWCNvmYlNiKBwpEXJ3SNDM6LQ6h_vbtzKggVlhL</ns2:sessionId>
  </ns1:SessionHeader>
 </soapenv:Header>
 <soapenv:Body>
  <create xmlns="urn:enterprise.soap.sforce.com">
   <sObjects xsi:type="ns3:Account" xmlns:ns3="urn:sobject.enterprise.soap.sforce.com">
    <ns3:Name>test08261045</ns3:Name>
    <ns3:BillingStreet>test08261045</ns3:BillingStreet>
    <ns3:BillingCity>test08261045</ns3:BillingCity>
    <ns3:BillingState>test08261045</ns3:BillingState>
    <ns3:BillingPostalCode>test08261045</ns3:BillingPostalCode>
    <ns3:BillingCountry>test08261045</ns3:BillingCountry>
    <ns3:ShippingStreet>test08261045</ns3:ShippingStreet>
    <ns3:ShippingCity>test08261045</ns3:ShippingCity>
    <ns3:ShippingState>test08261045</ns3:ShippingState>
    <ns3:ShippingPostalCode>test08261045</ns3:ShippingPostalCode>
    <ns3:ShippingCountry>test08261045</ns3:ShippingCountry>
    <ns3hone>test08261045</ns3hone>
    <ns3:Fax>test08261045</ns3:Fax>
    <ns3:AccountNumber>test08261045</ns3:AccountNumber>
    <ns3:Website>test08261045</ns3:Website>
    <ns3:Sic>test08261045</ns3:Sic>
    <ns3:TickerSymbol>test08261045</ns3:TickerSymbol>
    <ns3escription>test08261045</ns3escription>
    <ns3:Site>test08261045</ns3:Site>
   </sObjects>
  </create>
 </soapenv:Body>
</soapenv:Envelope>

 

here is the response that I received:

 

<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>
  <soapenv:Fault>
   <faultcode>soapenv:Server.userException</faultcode>
   <faultstring>common.exception.ApiException: Must send a concrete entity type.</faultstring>
   <detail>
    <sf:fault xsi:type="sf:InvalidSObjectFault" xmlns:sf="urn:fault.enterprise.soap.sforce.com">
     <sf:exceptionCode>INVALID_TYPE</sf:exceptionCode>
     <sf:exceptionMessage>Must send a concrete entity type.</sf:exceptionMessage>
    </sf:fault>
   </detail>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>

 

 

what did I do wrong here?

DevAngelDevAngel

Hi kpicha,

Looks like it should work.  How did you create the soap message?  Are you using axis or .net or php or something else?

DevAngelDevAngel

Oh, never mind, just saw your other post.  You are using VC++ I think.  Let me look at that post and see if there are more clues there.

 

DevAngelDevAngel
One more question, what is the url that you are sending this message to?
kpichakpicha

I'm using very low level CInternet objects to create HTTP requests from vc++

 

I can send you the entire code if you want it, but the info I posted on the original message was exactly what went out

 

Is this possibly a security issue ..?.. I was wondering if, as a developer, I would have the rights to be able to create instances of the Account object.

SuperfellSuperfell
What's the URL that you're sending that request to ? that looks like the error you'd get if you send your request to the partner endpoint, not the enterprise endpoint.
SuperfellSuperfell
I can't tell if its just a cut'n'paste error, but when i copied your message it has a space in the URI for the xsi namespace
xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance"

running your request like that generated the error you reported, if i remove the space, e.g. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" it worked (or at least got onto the next error about site not being valid for insert update, but that might just be my org configuration)
djordandjordan

I have seen that error when I accidentially used an EMEA server URL instead of the NA1 URL returned from the loginResponse

On instance does your SFDC org live?

Message Edited by djordan on 08-30-2004 04:18 PM