Useful to combine a LOT of individual Salesforce reports into ONE Word or Excel doc
Several 1000 rows per report are ok because we’re just merging a report into a document
Cannot update individual records so you won’t be able to use AC, SC, MFTS on those Accts, Opptys, whatever
Instead of this:
"&QueryID=[Revenue]a0336000000ELxK" +
You must do this:
"&QueryID=[Rev]a0336000000ELxK?pv0=" +
Each Operation is just one service event, even with 1000 rows in report
Conga Batch
The formula field is on a specific object and was converted from a solution (record-based merge).
Distributed Output:
Can use AC, SC, and MFTS on ALL records
Download or SendEmail or Docusign, etc
Common use case: weekly Invoice reminder, upcoming renewals
Advantage: customer can Download ONE document AND update all child records
Customers can send high quality Invoices with as many records as they want in a batch at a time, via email; however, larger batch operations must adhere to the following constraints:
Number of Salesforce API calls per day allowed by the Org
Salesforce file storage limits within the Org
Email provider (such as Salesforce, SendGrid, or AWS SES) limits on the number of emails to be sent per day
Consolidated Output:
Not useful as One Email, Executive Summary report
ONE document, i.e. a Batch document, must be limited to 200 records
The consolidated output limit can be increased to 500 records on request. To increase the limit, contact your Conga Representative.
A distributed (i.e. email) output is up to 1000 records
Can be a ListView
Each record = One Service Event, even if it’s a consolidated output equals multiple service events
Global Merge
The formula field is located on the Global Merge object and was converted from an Org-wide report.
Usually, just Download or Email
Very useful as an Executive Summary, can be sent to Board@mycompany
These are often scheduled, weekly reports
5 Salespeople, 5 batches, “weekly Sales status”
Useful to combine a LOT of individual Salesforce reports into ONE Word or Excel doc
Several 1000 rows per report are ok because we’re just merging a report into a document
Cannot update individual records so you won’t be able to use AC, SC, MFTS on those Accts, Opptys
Instead of this: "&QueryID=[Revenue]a0336000000ELxK" +
You must do this: "&QueryID=[Rev]a0336000000ELxK?pv0=" +
Each Operation is just one service event, even with 1000 rows in report