Data is displayed in the Template Builder to be accessed in the Conga Composer merge process.

The Master Object, identified with the ID parameter in the solution URL, determines what data is displayed in the Template Builder. Conga Composer retrieves all fields (both standard and custom) from the Master Object and displays them in the Template Builder so you have them available for merging into your template.

Conga Composer can also be run from the home page without a Master Object selected. This allows you to report organization-wide as you are not limited to a Master Object record. For more information, see Conga Global Merge for Solution Manager.

Solution URL with Opportunity as Master Object:

https://composer.congamerge.com?sessionId={!API.Session_ID}&serverUrl={!API.Partner_Server_URL_290} &id={!Opportunity.Id}

For example, if your solution URL contains &Id={!Opportunity.Id}, the Opportunity object is your Master Object, and you will place the Conga Composer button on the Opportunity page layout. Accordingly, the fields presented in the Master dataset on the Template Builder (or in the View Data workbook) will be primarily Opportunity fields.

The User and Org datasets appear in the Template Builder only if Track Activities is enabled for the Master Object. When using certain standard Salesforce objects (Account, Contact, Opportunity, or Quote) as the Master Object, Conga Composer also displays fields from related objects in the Master dataset.

The following fields are available when standard Salesforce objects are selected as the Master Object for Conga Composer: