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
kbkb 

field integrity exception inserting into Product entity

did something change w/ the product entity today??? our application was working for a long while (same code), and starting getting excpetions tonight...it inserts products into the product entity. today we started getting a field integrity exception. api 2.5 using axis 1.1, btw.

xml sent:

<?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:SessionHeader soapenv:mustUnderstand="0" xmlns:ns1="SoapService">
   <ns2:sessionId xmlns:ns2="urn:partner.soap.sforce.com">[removed]</ns2:sessionId>
  </ns1:SessionHeader>
 </soapenv:Header>
 <soapenv:Body>
  <create xmlns="urn:partner.soap.sforce.com">
   <sObjects xmlns:ns3="urn:sobject.partner.soap.sforce.com">
    <ns3:type>Product</ns3:type>
    <Name xsi:type="xsd:string" xmlns="">Content Management Server 2003</Name>
    <DefaultPrice xsi:type="xsd:double" xmlns="">700.0</DefaultPrice>
    <PricebookId xsi:type="xsd:string" xmlns="">00i30000000bp5wAAA</PricebookId>
   </sObjects>
  </create>
 </soapenv:Body>
</soapenv:Envelope>

respone:

<?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>
  <createResponse xmlns="urn:partner.soap.sforce.com">
   <result>
    <errors>
     <fields xsi:nil="true"/>
     <message>field integrity exception</message>
     <statusCode>FIELD_INTEGRITY_EXCEPTION</statusCode>
    </errors>
    <id xsi:nil="true"/>
    <success>false</success>
   </result>
  </createResponse>
 </soapenv:Body>
</soapenv:Envelope>

DevAngelDevAngel

Hi kb,

I've filed an engineering request for this issue.  Seems there is a server side issue.  I'll let you know via this thread when it is resolved.

 

kbkb
Thanks! Will look forward to a fix! We're disabled until then :-(
DevAngelDevAngel

Hi kb,

Was this working properly before?  What version and flavor of the API are using? (SOAP 2.5 or XML-RPC 1.9 etc)

kbkb

Yes, this was working before. Wed. evening was the last time it worked. Then Thurs night the failures started. We're using the SOAP partner API, v 2.5. What does the error mean? Does the server think we're provided a bad PriceBookID?

Let me know if you guys needs any info to diagnose...

DevAngelDevAngel

Hi kb,

No, after last nights release, something has regressed.  I'll post here when I know more.

DevAngelDevAngel

Hi kb,

This issue has been resolved.  Please post if you find this not to be the case.