How to Auto-Fill Customer Data into Templates
Learn what merge fields do, how S-Docs resolves them, and how to place one on a PDF-Upload template.
Last updated
Was this helpful?
Learn what merge fields do, how S-Docs resolves them, and how to place one on a PDF-Upload template.
Use this tutorial when you need to place live Salesforce data into a PDF template.
After setup, one generated PDF can show all of this:
Record data in fixed spots on the page
Different values for each Salesforce record
Reusable field placement across similar templates
This is the right starting point for forms, welcome packets, and branded PDFs.
Merge fields pull data from Salesforce into the generated document.
When S-Docs runs, it reads the source record, resolves each field path, and prints the value in the final output.
Common examples include:
Customer name
Billing address
Opportunity amount
S-Docs uses the template's Related To Type as the starting object.
From there, it can pull fields from that record and related records, such as Opportunity.Account.Name.
In a PDF-Upload template, you usually select the field in the editor instead of typing the syntax yourself.
S-Docs builds the field for you and lets you place it on the PDF canvas.
Use {{!Object.FieldName}} in the template body to print one field value.
Example: {{!Opportunity.Name}}
In PDF-Upload templates, the field picker usually generates the merge field for you.
One PDF-Upload template tied to a Salesforce object
One merge field placed on the PDF
One test document to confirm the output
Estimated time: 10 minutes
Before you start, make sure you have:
Access to S-Docs Templates
Permission to create or edit templates
A PDF file ready to upload
A test record with values you can verify
Go to S-Docs Templates.
Open an existing template or click New.
Set Related To Type to the object you want, such as Opportunity.
Set Template Format to PDF-UPLOAD.
Save the template.
This gives S-Docs the record type and PDF format needed for drag-and-drop field placement.
Problem: The field is placed, but the generated PDF has no value.
Solution:
Check that the source record has data in that field
Confirm the template uses the correct Related To Type
Reinsert the field if you selected the wrong path
Problem: The base record is correct, but the value lives on a parent record.
Solution:
Use the field picker to expand related records
Choose a path such as Opportunity.Account.Name
Test with a record that actually has that relationship populated
Problem: The value prints, but the placement is hard to read.
Solution:
Move the field to a wider area on the PDF
Test with shorter sample values first
Split long content across separate fields when needed
✅ What merge fields are used for ✅ How S-Docs resolves merge fields from Salesforce data ✅ The basic merge field syntax ✅ How to place a merge field on a PDF-Upload template
Use Template Attributes Tutorial when you need to format values.
Use Create Your First Template if you want the full PDF-Upload setup flow.
Use Getting Started with Conditional Logic when content should appear only for some records.
Add Opportunity.Name to a PDF template.
Add Opportunity.Account.Name below it.
Generate the document from two different records and compare the output.
Last updated
Was this helpful?
Was this helpful?

