Run a Batch Document Job from a Salesforce Report with Dochly
Before you run
Confirm these are ready before creating a batch job:
Output settings, storage, delivery, and notification defaults must be configured in Dochly → Batch Jobs → Settings. If not done yet, see Set up batch document processing first.
Run the Salesforce report and confirm the row count is exactly the intended record set. Every row becomes one generation — unexpected records in the report means unexpected documents sent to customers.
The template to be used has been previewed against a representative record from the report. All merge fields resolve correctly, conditional logic works as expected, and the output looks correct.
You have the Dochly Admin or Dochly User permission set assigned. Admins can create and configure jobs; Users can run pre-configured jobs. Verify in Setup → Users → Permission Set Assignments.
Report requirements
- Tabular or Summary report type — Matrix reports are not supported. Tabular is the simplest and most reliable format for batch source reports.
- Record ID column included — Dochly uses the ID column to identify which Salesforce record each row maps to. Without it, Dochly cannot match rows to records.
- Report type matches template object — an Opportunity template must run against an Opportunities report. Mismatched object types produce generation errors for every record.
- Saved in a shared or public folder — reports in personal folders are only accessible to the owner. Save it in a shared folder so Dochly can read it at job run time.
- Relative date filters where applicable — "This Month" beats "June 2026" for recurring jobs. Relative filters stay relevant on every re-run; static dates go stale.
Step-by-step: creating and running a batch job
Open New Batch Job
Navigate to the Dochly app → Batch Jobs tab → click New Batch Job. The job configuration panel opens. All fields in the panel are for this specific job run — they override the org-level defaults without changing those defaults for other jobs.
Name the job
Give the job a clear, descriptive name that identifies what it generates and when. Good naming makes the job history log easy to read.
- June 2026 Invoice Run — Closed Won
- Q3 Renewal Agreements — 90-Day Pipeline
- Annual Compliance Docs — All Active Accounts
Select the source report
In the Source section, select Salesforce Report as the source type. Search for and select the report. Dochly validates it immediately — showing row count, confirming the ID column, and checking the report type. If validation fails, the error message explains exactly what to fix.
Select the template
In the Template section, select the Active Dochly template for this job. Only Active templates are shown — Draft or Inactive templates are not available for batch jobs.
Configure per-job options
Override any org-level defaults for this specific job if needed:
Change the format from the default for this job only — e.g. generate DOCX for an internal review batch while the org default is PDF.
Enable or disable email delivery for this job specifically — useful for testing (disable delivery) or for one-off jobs that should email when the default does not.
Lower concurrency for very large jobs to avoid API rate limit errors. Higher concurrency for small urgent jobs where speed matters.
Use a different naming convention for this batch — e.g. include a batch-specific reference number or date prefix that differs from the standard template naming.
Review the confirmation summary and launch
Before launching, Dochly shows a confirmation summary:
Review the record count carefully before launching. Once started, emails go out to real recipients immediately and cannot be recalled. If the count is unexpected, cancel and re-check the report filters.
Click Launch Job. The job starts immediately and runs in the background. You can close the panel and continue working.
While the job runs
After launching, the job appears in Dochly → Batch Jobs → Active Jobs with a live progress indicator showing total records, processed so far, success count, failure count, and estimated time remaining. The job runs in the background regardless of whether you have the browser open.
The Active Jobs panel updates every 30 seconds. See Monitor and track batch jobs for full monitoring detail including failure log access and per-record status.
Dochly → Batch Jobs → Active Jobs → [Job Name] → Cancel. Records already processed keep their documents. Unprocessed records are skipped. Cancellation takes 1–2 minutes to propagate.
After the job completes
When all records are processed, the job moves to Job History with a completion status. Check the job summary for success count and failure details, and spot-check 3–5 records in Salesforce to confirm generated documents appear in Files with correct names and content.
Re-running a job
Dochly → Batch Jobs → Job History → [Job Name] → Run Again. Creates a new job instance with the same configuration — review and modify settings before launching. If you used a prevention field pattern, re-runs automatically skip already-processed records via the report filter.
For regular recurring jobs, use scheduled batch runs instead of manually re-running each time. Scheduled jobs trigger automatically at your configured interval.
Frequently asked questions
Your batch job is running. Next in this series: Schedule a batch document run in Salesforce with Dochly — automate recurring batch jobs to run on daily, weekly, or monthly schedules without manual intervention.
Rated 5 stars · Native Salesforce app · Free to install