Using SOQL Queries with Conga Composer

In addition to using Salesforce reports to gather information from Salesforce, you may also use SOQL queries.  SOQL queries are built and stored using the Conga Query Manager custom object.

The link to the private AppExchange listing for Conga Query Manager is located on our website.

This custom object stores Salesforce Object Query Language (SOQL) statements that will retrieve data related to the Master Object.

 



Using Queries instead of Reports

Conga Queries have certain strengths over the use of Salesforce Reports for gathering data:

  • Queries are slightly faster than Salesforce Reports
  • Queries can access objects that cannot be displayed in Salesforce Reports (e.g., Notes, Attachments, Approval History)
  • Queries reduce clutter on the Reports Tab
  • Queries have more restrictive security and visibility control options than Salesforce Reports
  • Queries are more reliable when multiple queries (e.g. over 10) are included in Conga Composer solution

Using Salesforce reports remains a wonderful option for basic requirements.
 

Warning! Conga Composer will retrieve a report (or query) that contains a maximum of 1,500 rows and contains less than 5 Mb of total data.
Additionally, each
Conga Composer solution has a combined row limit of 25,000.

 

The easiest way to build a Conga Query is through the Conga Query Builder.  The Query Builder is a four-step wizard that will guide you through the process of building a query by selecting a base object, choosing the columns (fields) you wish to expose, choosing appropriate selection criteria and testing your work.
 

Using the Conga Query Builder

To use the Conga Query Builder, follow these steps:
 
1. Click the “Conga Queries” tab from “All Tabs”

2. Click New to create a new record, enter a Name and Description, and then Save.

3. After returning to the “read” mode on the record, click the Conga Query Builder button to launch the wizard.





4. Select the base object.  The base object is the “lowest level” object from which you need to pull data. 
You’ll be presented with “higher-level” (parent) fields during the next step.




5. Select the columns you want to make available for merging.  The Query Builder also displays all of the Lookup fields (parent field relationships) from the base object.  You may include columns from any of the Lookup objects

 
 

 Tip!  Hover over a field name to see the API Name of the field.

 

Warning:  Some field names display differently than in the Salesforce user-interface, for example, “Phone” in Salesforce is shown as “Business Phone.”


6. Choose the selection criteria and sorting details.



 
Tip! Usually you choose the Master Object ID as the first “Field” and leave the corresponding “Value” column blank (much like the “pv0” value in a Salesforce Report).  Conga Composer will enter the Master Object ID into the Value when the button or link is launched.  in this way, you can filter the query according to whatever record from which you launch your Conga Composer solution.
 


7. Test your query by typing (or pasting) sample data to represent the values that will be passed in from your Conga Composer button or link.  Typically, the Master Object ID is pasted in the pv0 field.  Click Preview to test-run the query.




8. The results from the Preview display in a new, pop-up window. You may need to disable your pop-up blocker to view them.  Review the results to ensure the query is working properly.



 
8. Close the Preview results window and Save your query.


 
 
Warning! If you manually edit the SOQL query generated by the Query Builder,
do not use the Query Builder again for that query record because your edits will be overwritten.

Tip! You may copy/paste your SOQL Select Statement to the Description to have a secondary copy of it.