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
forceAMPforceAMP 

Query API call returns 15 char CreatedById values

The SOAP API doc says:

 

"an 18-digit, case-safe version of the ID is returned by all API calls"

 

Yet for some queries against the Case object, a 15 char id is returned.  See SOAP trace below.

 

It seems to be related to pulling the Chatter Answer Photo fields of the Case object.  If I remove those from the query, the Id's are returned as 18 char.

 

2013-06-05T18:27:00Z: Request::<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" xmlns:sfdc="urn:enterprise.soap.sforce.com" xmlns:sf="urn:sobject.enterprise.soap.sforce.com"><soapenv:Header><sfdc:CallOptions><sfdc:client>forceAMP/DBAmp/</sfdc:client></sfdc:CallOptions><sfdc:QueryOptions><sfdc:batchSize>2000</sfdc:batchSize></sfdc:QueryOptions><sfdc:SessionHeader><sfdc:sessionId>.......</sfdc:sessionId></sfdc:SessionHeader></soapenv:Header><soapenv:Body><sfdc:query><sfdc:queryString>select CreatedById,CreatorFullPhotoUrl,Id from case </sfdc:queryString></sfdc:query></soapenv:Body></soapenv:Envelope>

 

2013-06-05T18:27:01Z: Response::<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sf="urn:sobject.enterprise.soap.sforce.com"><soapenv:Body><queryResponse><result><done>true</done><queryLocator xsi:nil="true"/><records xsi:type="sf:Case"><sf:Id>50030000001VEgJAAW</sf:Id><sf:CreatedById>00530000000kQi6</sf:CreatedById><sf:CreatorFullPhotoUrl>https://c.na4.content.force.com/profilephoto/005/F</sf:CreatorFullPhotoUrl></records>

Ashish_SFDCAshish_SFDC

Hi Bill,

The issue was tracked and addressed; The occurrence is also listed on our Known Issues as Fixed in link below,
https://success.salesforce.com/issues_view?id=a1p30000000SxlGAAS
Please let us know if you have any further issues.

Regards,
Ashish, Salesforce.com
If this post answers your question, please mark this post as Solved.