Feedback
Did this article resolve your question/issue?

   

Article

How to query the Salesforce attachment associated with a particular instance of OPPORTUNITY table?

Information

 
TitleHow to query the Salesforce attachment associated with a particular instance of OPPORTUNITY table?
URL NameHow-to-query-the-Salesforce-attachment-associated-with-a-particular-instance-of-OPPORTUNITY-table
Article Number000186374
EnvironmentProduct: Connect for ODBC Salesforce driover
Version: All supported versions
OS: All supported platforms
Database: Salesforce
Application: All supported applications
Question/Problem Description
How to query the Salesforce attachment associated with a particular instance of OPPORTUNITY table while using the COnnect for ODBC Salesforce driver?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The Attachment table contains the field ParentID which is a reference to the ROWID of the row from the table to which the attachment is associated. Select the attachment data using a JOIN of the ATTACHMENT table to the OPPORTUNITY table.
For example:
SELECT a.NAME, a.DESCRIPTION, a.BODYLENGTH, a.BODY from ATTACHMENT a, OPPORTUNITY o where a.PARENTID=o.ROWID

It is recommended to add an additional WHERE clause values to limit the number of rows that the driver needs to get back from Salesforce in order to do the JOIN. Running the query without the additional where clause may cause the error :
OPERATION_TOO_LARGE: exceeded 100000 distinct ids in statement

This is because the driver needs to get all the rows from the table in order to do the JOIN within the cloud framework layer of the driver. Appending the ROWID value for the row from the opportunity table, the driver should be able to push the additional WHERE filters down to Salesforce to limit the number of rows that will be returned in order for the JOIN results to be assembled in the cloud framework layer of the driver.

One other thing to keep in mind is how cloud framework will evaluate the join. It will select all rows from the left table, then do a query per row in the left table to build the result set. It is best to have the smallest table to be the left most table in the join to achieve the best performance. This is true for all JOINS.
 
Workaround
Notes
Last Modified Date6/15/2016 1:50 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.