Guest Post: 3 Things Every Admin Should QA before Deploying a Conga Composer Solution

Subscribe to Our Blog

Get weekly updates
straight to your inbox

Submit your email address to subscribe.

By submitting this form you confirm that you agree to the storing and processing of your personal data by Conga as described in our Privacy Statement.

The Conga QA Team examines every exciting new feature of Conga and verifies that it is fit for public consumption. Here is their list of three things every admin needs to check before deploying a Conga solution to their end users.

  1. Know where your data is coming fromYou should already know what your master object is, now let’s make sure the data you have in Salesforce matches the data available in the View Data Workbook (VDW) and Template Builder. These can be found under ‘Tools & Settings’ in the Composer UI.


Even if the data shows up on your Salesforce Record, if it’s not in these two tools, Composer won’t be able to use it. If it’s on your Master Object, but you’re not able to see it in these tools, it’s usually an issue with Field Level Security.

The View Data Workbook is an Excel Spreadsheet of all the data being retrieved by Conga Composer.

pasted-image-0-(1)Maybe you have additional data you’re retrieving via reports or queries. You’ll want to make sure it’s showing up in the VDW and Template Builder under the correct dataset alias, or it will not be available for Composer to use.


All detail data gets its own tab in the VDW, labeled as the Alias you gave it in your URL. Since I’m using an opportunity as my Master Object, OppLineItems (Opportunity Products) are automatically retrieved as well.

Template builder


In the Template Builder, all data is displayed in dropdowns. Detail Data is under the dropdown labeled after the Alias you gave it in your button URL.

Whether you’re using reports or queries, Composer can retrieve almost any data for use in your custom solution. You’re probably already used to building Salesforce Reports, but don’t feel forced into them just because you’ve never used Queries. With Conga’s Query Builder, creating your own SOQL query is just as easy as creating a Salesforce report, no experience necessary!

To access the Conga Query Builder, go to the ‘Conga Queries’ Tab, create a new record, give it a name, and save the record. You should then see the ‘Conga Query Builder’ Button on the query record you’ve just created.


Follow the steps in the Conga Query Builder, and insert the Query ID into your button URL when finished*.  Once you’ve confirmed that all your data exists in the Template Builder and VDW as it should, you’re ready to check the next piece of your solution.

*An important note about adding ReportID’s and QueryID’s to your button URL; make sure you include an alias (&ReportID=[Alias]00O1123523XRrsf or &QueryID=[Alias]00O1123523XWrsf).

Redbox 1

Your solution will still work if you don’t, and you’ll still see your data, but every end user appreciates an alias, and as an additional benefit, it will make any troubleshooting you need to do as an admin much easier.

2. Check your template.

It’s absolutely imperative that you double check a few key components of your template before giving users access to the Composer solution. First, make sure all your static text (that is, text that isn’t populated by Conga Composer) is correct. There’s nothing more embarrassing than sending an email to all your customers with a glaring typo in it.

All your static text looks good? Good. Next up, we’re gonna need to double check your merge fields. Are you using Text Based or Traditional? If you’re using Text Based, all you’ll need to do is make sure the text inside the field codes “{{}}” matches the text you find inside the template builder.

redbox 2

Traditional merge fields will require an extra step,  which is hitting “Alt-F9”. This will toggle traditional field codes to ‘open’ thus showing you the juicy guts of your merge fields.


redbox 3

Once you’ve opened your fields up, make sure the text in between MERGEFIELD and /* MERGEFORMAT matches what you see in Template Builder.

Finally, you’ll want to make sure any detail regions (that is, data populated via a report or query ID), is nested inside TableStart and TableEnd fields.

redbox 4

Without these, Composer will assume you’re just using Master data merge fields, and none of your hard earned detail data will come through. Once you’ve followed these steps, all that data that we worked so hard to gather will come through looking just peachy.

3. Steer clear of URL errors

Last, but far from least, you’ll want to make sure your button URL doesn’t have any errors, as any of these will flush all the work we’ve done in the last two steps down the toilet. There are a number of ways a URL might be malformed, but one of the most common is having a space inside the URL. You’ll want to make sure there are no spaces anywhere in the URL, most of which are easy to find. That said, oftentimes there will be a space added at the end of a line in the URL, especially if the URL was brought over by copying and pasting.

redbox 5To quickly check for these, place your cursor on each row, and hit the ‘end’ key on your keyboard. This will take you to the end of the row, and if there’s a space between your cursor and the end of the parameter, delete it! Another very common issue is forgetting the ampersand “&” prefix to each parameter.

redbox 6

This is an even easier issue to check for, simply go through each parameter, and when you see one missing the ampersand, toss that sucker right in there.

redbox 7

Want to make sure your URL is properly formatted every time? Use the new Conga Solution Manager!

There you have it, folks, three essentials for every admin to check before deploying a solution, or when your solution isn’t working the way you’ve expected.

Tried these steps and still having trouble? Visit our support website, or give us a call at (866) 502-3334 for U.S Customers, at +44 (0) 203 608 0165 for EMEA customers, or +61 2 8417 2399 for our APAC Office, and one of our many talented and friendly BA’s will be happy to walk you through fixing any additional issues.


Leave a Reply

Your email address will not be published. Required fields are marked *