> This is part 1 of 4 of the full documentation (pages 1–100 of 333).
> The content is paginated: fetch every part to see all of it.
> Next part: https://help.sdocs.com/llms-full.txt/1
> Page index: https://help.sdocs.com/llms.txt
# Install S-Docs
Install S-Docs from Salesforce AppExchange and assign user permissions.
{% hint style="info" %}
Install S-Docs in a **Sandbox** or **Developer** organization first. Test the installation before installing it in a production org.
{% endhint %}
1\. Navigate to the [**Salesforce AppExchange listing**](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000003HeuPEAS).
2\. Select **Try It** for a Sandbox installation.
3\. Select **Get It Now** for a production or Developer organization installation.
4\. Confirm your details.
5\. Select **Continue to Installation**.
6\. Select **Log In & Install**.
7\. Select the Salesforce org where you want to install S-Docs.
8\. Select **Install for Admins Only**.
9\. Select **Install**.
{% hint style="info" %}
**Install for Admins Only** grants S-Docs access to the **System Administrator** profile and all custom profiles. Review Salesforce’s [package installation options](https://help.salesforce.com/s/articleView?language=en_US\&id=sf.distribution_installing_packages.htm\&type=5) for more restrictive access.
{% endhint %}
**Congratulations! S-Docs is now installed in your org.**
Assign the **SDocs User** or **SDocs Administrator** permission set to yourself and each user who uses S-Docs. Learn more in [Security and Permissions](/quick-start/getting-started/security-and-permissions).
# Connect S-Docs to your customer records
Configure S-Docs relationships for Salesforce standard and Custom Objects.
Once you have successfully installed S-Docs, the next step is configuring the application to recognize the specific Salesforce objects you plan to use for document generation.
To ensure S-Docs works seamlessly with your desired objects—whether they are standard Salesforce objects or custom ones—you must ensure the proper relational architecture is in place.
### Create a Lookup Field on the SDoc Relationship Object
To associate generated documents with your records, create a lookup field on **SDoc Relationship**. This field links the target object to S-Docs.
S-Docs includes lookup fields for standard objects, including **Account** and **Opportunity**. Check for an existing lookup field before you create one.
If the lookup field does not exist, create it. Custom Objects always require a new field. Some standard objects also require one.
1. Navigate to **Setup** > **Object Manager**.
2. Search for **SDoc Relationship**.
3. Select **SDoc Relationship**.
4. Select **Fields & Relationships**.
5. Select **New**.
6. Select **Lookup Relationship**.
7. Select **Next**.
8. Select the target object from the **Related To** list.
9. Select **Next**.
10. Enter a value in **Field Label**.
11. Enter a value in **Field Name**.
Enter the exact object name without `__c`. For example, enter `CustomObj` for `CustomObj__c`.
12. Select **Next**.
13. Select the checkbox for each relevant user.
14. Select **Next**.
15. Leave the default layout settings unchanged.
16. Select **Save**.
{% hint style="info" %}
For AppExchange packages, use `package_u_CustomObj` as the field name for `package__CustomObj__c`. Salesforce does not allow double underscores in the new field name.
{% endhint %}
### Add a Custom Object to the S-Doc Template Picklist
Complete this procedure when you configure S-Docs for a Custom Object. This lets you create S-Docs templates related to that object.
{% hint style="info" %}
This procedure uses `CustomObj__c` as an example. Replace it with your Custom Object API name.
{% endhint %}
1. Navigate to **Setup** > **Object Manager**.
2. Search for **S-Doc Template**.
3. Select **S-Doc Template**.
4. Select **Fields & Relationships**.
5. Search for **Related to Type**.
6. Select **Related to Type**.
7. Scroll to **Values**.
8. Select **New**.
9. Enter the Custom Object API name as a picklist value.
10. Select **Save**.
{% hint style="info" %}
For a Custom Object from an AppExchange managed package, enter the full API name. For example, enter `package__CustomObj__c`.
{% endhint %}
# Security and Permissions
To grant your team access to S-Docs, you need to configure security settings. Depending on your Salesforce environment, this involves up to two main steps: assigning package licenses and applying the correct permission sets.
> Best Practice Warning: Before configuring user permissions, we recommend reviewing standard Salesforce user management best practices. Always adhere to the principle of "Least Privilege"—starting users with a minimum access profile and layering on permission sets only as needed based on their job functions.
### Part 1: Licenses (Production vs. Sandbox)
Before you begin assigning licenses, you need to determine if your current environment actually requires them.
If you are installing in a Sandbox environment: You do not need to assign licenses. S-Docs provides site-wide licensing automatically in sandboxes. You can skip this entire section and move directly to Part 2: Permission Sets.
If you are installing in a Production environment: You must have a license, but the type of license you purchased dictates your next steps:
* Site License: If your organization purchased a Site License, S-Docs is automatically licensed for all users in your org. You do not need to assign seats manually. Skip to Part 2: Permission Sets.
* Seated License: If your organization purchased a specific number of seats, you must manually assign those licenses to individual users. Follow the steps below.
### How to Assign Individual Licenses (Seated Production Orgs Only)
1. Navigate to the Setup menu by clicking the gear icon in the upper right corner.
2. Type Installed Packages into the Quick Find bar and select it from the drop-down menu.
3. Find the S-Docs package in your list of installed packages and click Manage Licenses.
4. On the Package Manager page, click the Add Users button.
5. Use the checkboxes to select yourself and any other users who need access to S-Docs.
6. Click Add at the bottom of the screen.
Your selected users will now appear in the Licensed Users list. You do not have to assign all of your available licenses at once; you can return to this page to add or remove users at any time.
### Part 2: Permission Sets
Regardless of whether you are in a Sandbox or Production environment, all users must be assigned permission sets to use S-Docs.
S-Docs provides several out-of-the-box permission sets. For standard internal setup, you will primarily use the following two:
* SDocs Administrator: Grants full access to S-Docs, including the template editor and S-Docs Setup tab. Assign this to users who will be building templates and managing the app's configuration.
* SDocs User: Designed for standard internal users. It grants them the access required to generate documents and insert S-Docs Jobs but restricts them from altering templates or backend configurations.
### Additional Permission Sets
Depending on your organization's specific workflow and additional add-ons, you may also utilize the following permission sets:
* SDocs LWC Community User: Ensures that Experience Cloud users can interact with S-Docs Lightning Web Components.
* S-Doc eSignature Requester: Allows users to send e-signature requests (requires S-Sign).
* S-Doc eSignature Signer: Assigned to the site guest user profile associated with an Experience Cloud site created for the e-signature interface.
* SDocs Jobs (Guest Users) (legacy): Grants a website guest user the ability to insert SDoc Jobs.
* **Note**: The "S-Doc Site Guest User" permission set is deprecated.
### For Example:
| S-Docs Permission Set | Target Roles / Users | Example Scenarios |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| SDocs Administrator | \*Salesforce Administrators\*Business Analysts\* Operations Managers\* Document Template Creators | \* Alex, the Admin: Needs to design an automated invoice template, map Salesforce fields, and configure the S-Docs global settings. |
| SDocs User |
\* Sales Representatives \* Customer Success Agents \* Field Service Technicians \* HR Personnel
| \* Sarah, the Account Executive: Needs to click the "Generate Proposal" button on an Opportunity record to send a PDF to a client, but shouldn't be altering the legal language/content within the template. |
| SDocs LWC Community User |
| \* John, a Partner Community User: Logs into your portal and needs to generate a dynamic compliance report using an S-Docs Lightning Web Component embedded on his dashboard. |
| S-Doc eSignature Requester |
| \* Elena, the Contract Manager: Needs to send a newly generated Sales Agreement out to a client for secure digital signing via e-Sign. |
| S-Doc eSignature Signer | \* Site Guest User Profile (associated with your public-facing Experience Cloud site) | \* Public/External Signers: A client receives an email link to sign a contract. Salesforce uses this background guest profile to allow them to securely view and sign the document without logging in. |
# Create Your First Template
Welcome! If you are a new Salesforce Administrator looking to quickly generate beautiful, data-driven documents, you are in the right place. Creating templates from scratch using HTML and CSS can feel a bit daunting at first, but S-Docs has a fantastic feature designed specifically for you: the PDF-Upload template format.
Let's walk through exactly what this feature is, how to enable it, and the step-by-step process of building your very first drag-and-drop template.
***
### Introduction to PDF-Upload Templates
What are PDF-Upload templates? Simply put, PDF-Upload templates allow you to take a pre-existing, standard-formatted PDF (like a fillable form or a beautifully designed marketing brochure) and upload it directly into S-Docs. From there, you can use a simple drag-and-drop interface to merge your Salesforce data directly onto the document. You get to skip the process of rebuilding the document from scratch using HTML or CSS!
When should you use them? PDF-Upload templates are your best friend when you have:
* Design-heavy documents that were created by a marketing or design team (where rebuilding the exact layout in HTML would be time-consuming).
* Basic documents that only require simple, straightforward field merges (like placing a Contact Name and Account Address on a static form).
***
### Step 1: Creating Your First Template Record
Let's create the shell for your new template.
1. Open the App Launcher (the 9-dot grid on the top left) and search for S-Docs.
2. Click on the S-Docs Templates tab, then click the New button.
3. Fill out the required fields to set up your template:
* Template Name: Give it a clear, descriptive name (e.g., "Customer Welcome Packet").
* Related to Type: Select your base object. This is the primary record you will generate the document from (e.g., Opportunity or Contact).
* Template Format: Select PDF-UPLOAD from the drop-down.
4. Click Save.
5. Once saved, look at the top right of the record page. Click the dropdown arrow and select the Template Editor button to launch the designer.
***
### Step 2: Uploading Your PDF
Welcome to the Template Editor! Let's get your PDF onto the canvas.
1. Locate the PDF File Quality drop-down menu. You can choose from Full, High, Medium, or Low.
* *Note: Higher quality will look crisper but will result in a larger generated file size. High or Medium is usually the sweet spot for standard business documents.*
2. Click the Upload PDF File button and select the local PDF file from your computer.
Once uploaded, your PDF will appear on the right side of the screen, and your building tools will appear on the left.
***
### Step 3: Adding & Formatting Merge Fields
This is where the magic happens! On the left side of the editor, you will see two main menus:
* PDF-Upload Settings: This is used to apply global CSS styling that affects *all* fields on your document.
* S-Docs Fields: This is where you configure and grab the individual Salesforce merge fields to drop onto your PDF.
Let's add your first field:
1. Under the S-Docs Fields menu, click Create Another Field.
2. Select Merge Field as your field type.
3. Click the Select Merge Field button. This opens a window showing all the fields available on your base object.
* *Pro-Tip: You can pull data from related objects (up to 3 levels deep) by clicking on fields that have a `>` symbol next to them!*
4. Select your desired field and click Insert Field.
> ⚠️ Warning: The Crucial CSS Tip! By default, text merged onto a PDF-Upload template will *not* wrap; if the text is too long, it will run right off the side of the page! To prevent this, locate the Additional Style box for your specific field and type in the following: `white-space: normal !important; max-width: 200px;` *(You can adjust the "200px" number based on how wide you want the text block to be).*
Adding Conditional Logic (Optional): Only want a field to show up under certain conditions? Use the Render If box! For example, if you only want an address to appear when an Opportunity is closed, you would enter: `{{!Opportunity.stagename}} == 'Closed'`.
Place the Field: Once your field is configured, you'll see a generated drag-and-drop block (e.g., SDOCS INPUT ID=1). Simply click, hold, and drag this block exactly where you want it to appear on the PDF canvas on the right.
***
### Limitations & Best Practices
To set you up for success, it's important to know the boundaries of the PDF-Upload format. While incredibly fast and user-friendly, it trades a bit of complexity for ease of use. Keep these limitations in mind:
* File Type: PDF is the *only* supported file type for upload.
* Advanced Features: Complex data structures like Related Lists (tables of child records) and nested conditional renders are NOT supported in this format. (If you need these, use the standard HTML/PDF template format!).
* Editor Tabs: The standard Template Headers, Footers, and Page Settings tabs are not available in this mode, as those elements should already be baked into the PDF you are uploading.
***
Congratulations! You've just learned how to build a PDF-Upload template. You are well on your way to becoming an S-Docs power user.
# Configure Document Generation
If this is your first hands-on S-Docs setup, start here. S-Docs Lightning Web Components give you a simple, native way to generate documents directly from a Salesforce record page.
You do not need to build a custom interface or write code to get started. Add the components in Lightning App Builder, choose a few settings, and users get a clean generate-review-send workflow in one place.
## What You'll Build
In this tutorial, you'll add S-Docs Lightning Web Components to a Salesforce Lightning record page.
By the end, you'll have:
* A **Generate Documents (S-Docs)** component on a record page
* A **Documents (S-Docs)** component below it
* Optional email, refresh, versioning, and Live Edit features configured
* A tested record-page workflow for end users
## Prerequisites
Before starting, make sure you have:
* Complete [Create Your First Template](/quick-start/getting-started/create-your-first-template)
* Permission to edit Lightning record pages
* A test record for that object
* Access to Lightning App Builder
* The target object's API name, such as `Account`, `Opportunity`, or `Case`
If you plan to enable optional features, also confirm:
* You have an HTML email template ready for email actions
* Your template supports Live Edit if you want inline editing
* Your template is configured correctly for the output format you want to generate
{% hint style="info" %}
Documents generated from these components are saved as Salesforce Files and linked to the record.
{% endhint %}
{% stepper %}
{% step %}
#### Step 1: Pick the record page and test record
Choose the object where users will generate documents.
Then open one real record for that object.
Use this record later to test the page after configuration.
{% endstep %}
{% step %}
#### Step 2: Open Lightning App Builder
1. Open your test record.
2. Click on the **Settings/Gear** Icon
3. Select **Edit Page**
**Or**
1. Click **Setup**.
2. Go to **Object Manager**.
3. Open your target object.
4. Select **Lightning Record Pages**.
5. Open the page you want to edit.
6. Click **Edit**.
This opens **Lightning App Builder**.
{% endstep %}
{% step %}
#### Step 3: Add the Generate Documents component
1. In the component panel, search for **S-Docs**.
2. Drag **Generate Documents (S-Docs)** onto the page.
3. Place it where users should start the workflow.
A top section or left column usually works best.
{% endstep %}
{% step %}
#### Step 4: Configure Generate Documents (S-Docs)
Select the component and set the core properties.
Recommended starting configuration:
* **Title:** `Templates to Generate`
* **Object API Name:** your base object, such as `Account`
* **Template Name** or **Template IDs or Names:** choose the templates users should see
* **Notify User:** enabled
* **Open Preview:** enabled if users should review documents immediately
Use these options only when needed:
* **Allow Users to Select Templates** when users should choose from multiple templates
* **Reuse Template for Multiple Documents** when one template should generate several documents in one flow
{% endstep %}
{% step %}
#### Step 5: Add the Documents component
1. Search for **S-Docs** again.
2. Drag **Documents (S-Docs)** onto the same page.
3. Place it directly below **Generate Documents (S-Docs)**.
This gives users a clean top-to-bottom workflow:
1. Generate documents
2. Review generated files
3. Email, refresh, edit, or inspect versions
{% endstep %}
{% step %}
#### Step 6: Configure Documents (S-Docs)
Select **Documents (S-Docs)** and configure the features your users need.
Recommended starting configuration:
* **Title:** `Generated Documents`
* **Object API Name:** the same object used in the Generate Documents component
Optional configuration:
* Add an **Email Template** if users should send documents with a predefined message
* Enable **Automatically Open Email Editor** if users usually email right after generation
* Enable **Show Refresh** if users need to update document data after record changes
* Enable **Show Versions** if users need version history on refreshed or edited documents
{% endstep %}
{% step %}
#### Step 7: Save and activate the page
1. Click **Save**.
2. Click **Activate** if the page is not already active.
3. Assign the page as needed for app, record type, or profile.
Then return to your test record.
{% endstep %}
{% step %}
#### Step 8: Test document generation
On the record page:
1. Find **Templates to Generate**.
2. Generate one document.
3. Confirm the document appears in **Generated Documents**.
4. Confirm the file is linked to the record.
5. If **Open Preview** is enabled, confirm the preview opens automatically.
Your base record-page setup is now complete.
{% endstep %}
{% endstepper %}
## Turn On Optional Features
Use the options below to expand the workflow.
### Send generated documents by email
Configure an [email template](/quick-start/template-building/create-your-first-email-template) in the **Documents (S-Docs)** component when users send the same type of message often.
You can also enable **Automatically Open Email Editor** to open email right after generation.
For setup details, see [How To: Sending Generated Documents via Email](/sdocs/automation-and-document-lifecycle/workflows/sending-generated-documents-via-email-s-docs-lwc).
### Refresh document data
Enable **Show Refresh** in the **Documents (S-Docs)** component when users need updated field values in an existing document.
Refresh updates the document content and creates a new version.
For details, see [How To: Refresh Document Data Within the Documents](/sdocs/automation-and-document-lifecycle/workflows/refresh-document-data-within-the-documents-s-docs-lwc).
### Show document versions
Enable **Show Versions** when users need to review earlier document states.
This works best with **Refresh Data** and **Live Edit**.
For details, see [How To: View Document Versions in the Documents LWC](/sdocs/automation-and-document-lifecycle/workflows/view-document-versions-in-the-documents-lwc).
### Enable Live Edit
Live Edit is controlled on the template.
To enable it:
1. Open the S-Docs template record.
2. Open the template editor.
3. Go to **Document Options**.
4. Under **Attachment & File Options**, enable **Allow Edit**.
5. Save the template.
After that, users can edit supported generated files from the **Documents (S-Docs)** component.
For details, see [How To: Editing Generated Documents](/sdocs/automation-and-document-lifecycle/workflows/editing-generated-documents-live-edit).
## Recommended Admin Setup
For most internal Lightning record pages, start with this pattern:
* **Generate Documents (S-Docs)** at the top
* **Documents (S-Docs)** directly below it
* **Notify User** enabled
* **Open Preview** enabled
* **Show Refresh** enabled when record data changes often
* **Show Versions** enabled when auditability matters
* A predefined [email template](/quick-start/template-building/create-your-first-email-template) when users send the same document type repeatedly
This keeps generation and post-generation actions in one place.
## Common Issues
Templates do not appear in the Generate Documents component
Check these items:
* The template is built for the same base object as the record page
* The template name or ID was entered correctly
* The user has access to the template
* The component's **Object API Name** matches the record page object
The document generates, but it does not appear in Generated Documents
Check these items:
* Both components use the same object configuration
* The document was created as a Salesforce File
* The page was saved and activated after configuration
* The record was refreshed after generation
Refresh or Versions options do not appear
Check these items:
* **Show Refresh** is enabled for refresh actions
* **Show Versions** is enabled for version history
* The page was saved and activated after changes
Edit does not appear for a generated document
Check these items:
* **Allow Edit** is enabled on the template
* The generated format supports Live Edit
* The document came from a template that has Live Edit enabled
DOCX generation does not work as expected
Check the template configuration.
For DOCX output, enable **New Microsoft Template Upload** on the template.
## What You've Built
You now have a Lightning record page where users can:
* Generate documents from S-Docs templates
* Review generated files without leaving the record
* Email documents
* Refresh document data
* View document versions
* Edit supported documents when Live Edit is enabled
### Continue with tutorials
Ready for more hands-on practice? These tutorials cover the most common next steps.
* [Configure Email Sending On Your Record Page](/quick-start/document-generation/configure-email-sending-on-your-record-page)
* [Getting Started: Automate Document Generation](/quick-start/document-generation/getting-started-automate-document-generation)
* [Getting Started: Automate Emails](/quick-start/document-generation/getting-started-automate-emails)
# Generate and Email Your Document
Generate a document from a Salesforce record page, review it, and send it by email with the S-Docs Lightning Web Components.
## What You'll Learn
* Generate a document from a Salesforce record page
* Review the generated file in the document list
* Open the email editor from the generated document
* Check recipients, subject, and sender details before sending
* Troubleshoot the most common end-user issues
## What You'll Build
In this tutorial, you will use an `Opportunity` record to generate a quote and email it to a customer.
By the end, you will have:
* One generated quote linked to the `Opportunity`
* One reviewed PDF ready to send
* One outbound email sent from the record page
* One repeatable workflow your team can use every day
**Estimated time:** 10 minutes
## Prerequisites
Before you start, make sure you have:
* Access to an `Opportunity` record page with **Generate Documents (S-Docs)** and **Documents (S-Docs)**
* At least one S-Docs template available in the generation list
* One test `Opportunity` with customer data
* Permission to generate documents and send email from Salesforce
* Email Deliverability set to All Emails in Setup
* An admin-configured email template if you expect default subject or recipient values
If the S-Docs components do not appear on the record page, ask your Salesforce admin to complete [Add S-Docs Lightning Components to a Record Page](/quick-start/document-generation/add-s-docs-lightning-components-to-a-record-page).
{% stepper %}
{% step %}
### Step 1: Open the record where you want to send the document
Start on the Salesforce record that holds the customer data.
For this example, use an `Opportunity`.
1. Open Salesforce.
2. Go to **Opportunities**.
3. Open one test opportunity.
4. Confirm the record has the customer and quote details you want to send.
You are now on the record page where the full generate-and-send workflow happens.
{% endstep %}
{% step %}
### Step 2: Generate the document
Use the S-Docs generation panel at the top of the record page.
You may see it labeled **Generate Documents (S-Docs)** or a custom title such as `Templates to Generate`.
1. Find the S-Docs generation panel.
2. Select the template you want, such as a quote template.
3. Click **Generate**.
4. Wait for the success notification if **Notify User** is enabled.
This creates the document from the record data.
{% hint style="info" %}
If your page is configured to open previews automatically, the generated document may open right away.
{% endhint %}
{% endstep %}
{% step %}
### Step 3: Confirm the document appears in the document list
After generation, the file should appear in the S-Docs document list on the same page.
{% hint style="warning" %}
Note: You may need to refresh the page to ensure the document is visible in the Generated Documents component.
{% endhint %}
You may see it labeled **Documents (S-Docs)** or a custom title such as `Generated Documents`.
1. Scroll to the S-Docs document list.
2. Look for the new file you just generated.
3. Confirm the file name matches the document you expected.
4. Confirm the document is tied to the same `Opportunity`.
This confirms the document was created and linked to the record.
{% endstep %}
{% step %}
### Step 4: Review the document before you send it
Check the file before you email it.
1. Open the generated document from the list.
2. Review key details such as customer name, amount, and date.
3. Close the preview when you are done.
This helps you catch record-data issues before the customer sees the document.
{% endstep %}
{% step %}
### Step 5: Open the email editor
Use the email action from the generated document.
Depending on your page setup, this can appear as an **Email** action on the document row or as an action after you select the document.
1. Find the generated document in the list.
2. Open the email action for that document.
3. Wait for the email editor to load.
If your admin enabled automatic email open, the editor may appear right after generation instead.
{% endstep %}
{% step %}
### Step 6: Review the email details and send
Check the message before you send it.
1. Confirm the **To** address is correct.
2. Confirm the **Subject** matches the document you are sending.
3. Confirm the **From** address matches your team's process.
4. Review the email body.
5. Make edits if your org allows them.
6. Click **Send**.
What you just did:
* Used the generated document as the source for the outbound email
* Confirmed recipient and sender details before sending
* Completed the full workflow without leaving the record page
{% endstep %}
{% step %}
### Step 7: Verify the result on the record
Do one quick check after sending.
1. Return to the `Opportunity` record if the editor closed.
2. Confirm the generated document still appears in the document list.
3. Confirm the workflow completed without an error.
4. If needed, check the record's **Files** related list.
You now have a complete record-page workflow for generating and emailing S-Docs output.
{% endstep %}
{% endstepper %}
## Common Issues and Solutions
I do not see any templates in the generation panel
Check these items:
* The page includes **Generate Documents (S-Docs)**
* Your admin added templates to the component setup
* The template matches the same base object as the record
* You have access to the template
If the panel is empty, ask your Salesforce admin to review [Configure Document Generation](/quick-start/getting-started/configure-document-generation).
The document generated, but I cannot find it
Check these items:
* Refresh the record page
* Confirm the page includes **Documents (S-Docs)**
* Confirm the generation finished without an error
* Check the record's **Files** related list
The email editor opens, but the recipient is blank
Check these items:
* The source record contains the expected email address
* Your admin configured email defaults on the template
* You can type the address manually if your org allows it
If email defaults are expected but missing, ask your admin to review [Configure Email Template Settings](/quick-start/template-building/customize-template-settings-email).
I cannot send the email
Check these items:
* All required email fields are completed
* Your Salesforce user can send email
* The sender option configured by your admin is valid
* Your org did not apply a sending restriction that blocks the address
The document content looks wrong
Check these items:
* The source record has the correct data
* You generated from the correct template
* You opened the newest generated file
If the layout or default values are wrong, share the issue with the template owner or Salesforce admin.
## What You've Learned
✅ Generated a document from a Salesforce record page\
✅ Confirmed the file appeared in the S-Docs document list\
✅ Opened the email editor from the generated document\
✅ Reviewed recipient, subject, and sender details\
✅ Sent the document without leaving the record page
## Next Steps
* Use [Configure Email Template Settings](/quick-start/template-building/customize-template-settings-email) if your team wants email defaults.
* Use [Configure Template Settings: Document Generation](/quick-start/template-building/customize-template-settings-document-generation) if your team wants cleaner file names and save behavior.
* Use [Add S-Docs Lightning Components to a Record Page](/quick-start/document-generation/add-s-docs-lightning-components-to-a-record-page) if your admin still needs to set up the page.
## Practice Exercise
Send one test quote from an `Opportunity` record.
1. Open a test opportunity.
2. Generate one quote document.
3. Review the file.
4. Email it to yourself.
5. Confirm the email arrives with the expected subject and attachment.
Bonus challenges:
* Generate a second template from the same record.
* Send the document to a different test address.
* Update the `Opportunity`, regenerate the file, and compare the result.
# Auto-fill customer data in Document Templates
Add Merge Fields to PDF-Upload Document Templates and generate documents with Salesforce record data.
Use this tutorial to place Salesforce record data into a PDF-Upload Document Template.
### Previewing Generated Output
After setup, each generated PDF can include:
* Record data in fixed page locations
* Different values for each Salesforce record
* Reusable field placement across similar Document Templates
Use this approach for welcome packets and branded PDFs.
### Understanding Merge Fields
Merge Fields pull Salesforce data into generated documents.
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 names
* Billing addresses
* Opportunity amounts
### Understanding Merge Fields in S-Docs
S-Docs uses the Document 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 Document Template, select the field in the editor.
S-Docs creates the Merge Field and adds it to the PDF canvas.
### Using Merge Field Syntax
Use `{{!Object.FieldName}}` in the Document Template body to print one field value.
Example: `{{!Opportunity.Name}}`
{% hint style="info" %}
The field picker creates Merge Fields in PDF-Upload Document Templates.
{% endhint %}
### Add a Merge Field to a PDF-Upload Document Template
#### Reviewing the configuration
* One PDF-Upload Document Template tied to a Salesforce object
* One Merge Field placed on the PDF
* One test document to confirm the output
**Estimated time:** 10 minutes
#### Meeting prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates**
* Permission to create or edit Document Templates
* A PDF file ready to upload
* A test record with values you can verify
{% stepper %}
{% step %}
#### Create a PDF-Upload Document Template
1. Navigate to **S-Docs Templates**.
2. Click **New**.
3. Set **Related To Type** to the required object, such as `Opportunity`.
4. Set **Template Format** to `PDF-UPLOAD`.
5. Click **Save**.
S-Docs uses these settings for drag-and-drop Merge Field placement.
{% endstep %}
{% step %}
#### Upload the PDF
1. Open the Document Template.
2. Click **Template Editor**.
3. Click **Upload PDF File**.
4. Select the PDF file.
The PDF appears on the canvas. The field tools appear on the left.
Download the sample PDF file for reference.
{% file src="/files/xk7rv0Lq1oaDi88B8YdL" %}
{% endstep %}
{% step %}
#### Create a Merge Field
1. In **S-Docs Fields**, click **Create Another Field**.
2. Select **Merge Field**.
3. Click **Select Merge Field**.
4. Choose a field, such as `Opportunity.Name` or `Opportunity.Account.Name`.
5. Click **Insert Field**.
S-Docs creates the Merge Field from the selected Salesforce path.
{% endstep %}
{% step %}
#### Place the Merge Field on the PDF
1. Find the generated field block in the left panel.
2. Drag it onto the PDF canvas.
3. Drop it where the value should appear.
S-Docs prints the field value in this location.
{% endstep %}
{% step %}
#### Test the Document Template
1. Click **Save**.
2. Open a test record for the same object.
3. Click **Generate Document**.
4. Confirm the PDF shows the expected value in the right spot.
If the value is incorrect or blank, check the source record and field selection.
{% endstep %}
{% endstepper %}
### Resolving Common Issues
### **The Merge Field shows blank in the PDF**
Verify that the source record contains data. Confirm **Related To Type** matches the source object. Reinsert the Merge Field if you selected an incorrect path.
### **You need data from a related record**
Expand related records in the field picker. Select a path such as `Opportunity.Account.Name`. Test with a record that includes the relationship.
### **The Merge Field placement looks incorrect**
Move the Merge Field to a wider PDF area. Test with shorter sample values. Split long content across separate fields when needed.
### Reviewing What You Learned
* Merge Fields add Salesforce data to generated documents.
* S-Docs resolves Merge Fields from Salesforce record data.
* PDF-Upload Document Templates support drag-and-drop Merge Field placement.
### Continuing to Related Tasks
* Use [How to Format Text, Dates, and Currency](/quick-start/template-building/how-to-format-text-dates-and-currency) to format values.
* Use [Create Your First Template](/quick-start/getting-started/create-your-first-template) for the full PDF-Upload setup flow.
* Use [How to Show or Hide Content Automatically](/quick-start/template-building/conditional-logic-tutorial) when content appears for selected records.
### Practicing Merge Field Placement
1. Add `Opportunity.Name` to a PDF-Upload Document Template.
2. Add `Opportunity.Account.Name` below it.
3. Generate the document from two different records and compare the output.
# Customize Template Settings: Document Generation
Configure page layout, file naming, and file save behavior for a quote Document Template.
Use this tutorial when you want one Document Template to generate polished quotes with consistent layout and file handling.
## Reviewing expected results
After setup, one generated quote gives you:
* A PDF with a consistent file name, such as `Quote-Acme Corporation-2026-04-09.pdf`
* A Salesforce File linked to the Opportunity
* Page spacing that leaves room for company letterhead
Use this configuration for quote, invoice, and renewal Document Templates that need predictable output.
## Choosing Document Template settings
Use Document Template settings when you need predictable output from one Document Template.
**Best for:**
* Quote Document Templates with fixed page layout and file naming
* Invoice Document Templates that should save as Salesforce Files
* Renewal or contract Document Templates with consistent output formatting
Use another feature when the problem is different:
* Use [How to Show or Hide Content Automatically](/quick-start/template-building/conditional-logic-tutorial).
* Use [Adding Tables (Like Products or Contacts) to Your Document](/quick-start/template-building/adding-tables-like-products-or-contacts-to-your-document).
* Use [How to Format Text, Dates, and Currency](/quick-start/template-building/how-to-format-text-dates-and-currency).
## Configure settings for a quote Document Template
### Configure These Settings
* Custom page margins for letterhead
* An automatic output file name
* Automatic file save behavior
**Estimated time:** 15 minutes
### Meet Prerequisites
Before starting, make sure you have:
* An existing S-Docs Document Template
* The Document Template's **Related To Type** set to `Opportunity`
* Permission to edit S-Docs Document Templates
* At least one Opportunity with an Account and line items for testing
* Basic familiarity with Merge Field syntax
If you do not have a starter Document Template, create one first.
{% stepper %}
{% step %}
### Open the Document Template Editor
1. Navigate to **S-Docs Templates**.
2. Open your quote Document Template.
3. Click **Edit Template**.
4. Confirm the editor shows tabs such as **Page Settings**, **Document Options**, and **Email Settings**.
You are now in the screen where all Document Template settings appear.
{% endstep %}
{% step %}
### Set Page Margins for Letterhead
Use custom margins when your company header is already printed or built into the design.
1. Open **Page Settings**.
2. Set **Page Layout** to `Custom`.
3. Enter these values:
* **Page Width:** `8.5`
* **Page Height:** `11`
* **Top Margin:** `2`
* **Bottom Margin:** `1`
* **Left Margin:** `0.75`
* **Right Margin:** `0.75`
* **Unit:** `inches`
This leaves extra room at the top and keeps body content readable.
{% endstep %}
{% step %}
### Set the Output File Name
This controls the file name you see in Salesforce and email attachments.
1. Open **Document Options**.
2. Find **Attachment & File Name Options**.
3. In **Output File Format**, enter:
{% code title="Output file format" %}
```
Quote-{!Opportunity.Account.Name}-{!TODAY()}.pdf
```
{% endcode %}
A generated file now follows one consistent pattern.
Example output: `Quote-Acme Corporation-2026-04-09.pdf`
{% hint style="info" %}
Use single-brace Merge Fields like `{!Opportunity.Name}` in settings tabs. Use double-brace Merge Fields like `{{!Opportunity.Name}}` in the Document Template body.
{% endhint %}
{% endstep %}
{% step %}
### Save the Generated Document as a Salesforce File
This keeps each generated quote attached to the source record.
1. Stay in **Document Options**.
2. Under **Attachment & File Options**, enable **Create Salesforce File and link to record**.
3. Leave **Delete related Salesforce Attachment/File upon S-Doc deletion** enabled.
Each generated quote now appears in the record's **Files** related list.
{% endstep %}
{% endstepper %}
Save the Document Template. Then generate one test document.
Verify these results:
* The file name matches your expected pattern.
* The quote appears in the **Files** related list.
* The top margin leaves room for letterhead.
## Applying guardrails and limits
### Follow Merge Field Rules
* **Use** single braces in settings tabs.
* If you mix syntax or casing, values can print as raw text or stay blank.
### Configure File Behavior
* **Enable** Salesforce Files in your org if your team saves generated documents there.
* **Expect** the generated file to link back to the source record when file creation is enabled.
### Follow Testing Rules
* **Test** with an Opportunity that already has real account data.
* **Generate** a fresh document after each settings change.
* **Verify** the file name, Files related list, and page spacing every time.
* If you skip testing, layout and file issues can surface after you generate live documents.
# Customize Template Settings: Email
Configure default email subject, recipients, sender behavior, and sending guardrails for a quote Document Template.
Use this tutorial when you want one Document Template to generate a document with email defaults.
## Reviewing expected results
After setup, one generated quote gives you:
* A prefilled subject, such as `Quote for Renewal - Acme Corporation`
* A default recipient pulled from the related record
* A defined sender option for consistent outbound email
* Optional restrictions that prevent editing or sending to the wrong domain
Use this configuration for quote, invoice, and renewal Document Templates you email often.
## Choosing email settings
Use email settings when you need predictable email behavior from one Document Template.
**Best for:**
* Quote Document Templates with a default subject and recipient
* Invoice Document Templates that should send from one approved address
* Contract Document Templates that need locked email content or domain limits
Use another feature when the problem is different:
* Use [Create Your First Email Template](/quick-start/template-building/create-your-first-email-template).
* Use [Configure Email Sending On Your Record Page](/quick-start/document-generation/configure-email-sending-on-your-record-page).
* Use [Getting Started: Automate Emails](/quick-start/document-generation/getting-started-automate-emails).
## Configure email settings for a quote Document Template
### Configure These Settings
* A default email subject
* Default email recipients
* Sender behavior for outbound email
* Optional sending restrictions
**Estimated time:** 15 minutes
### Meet Prerequisites
Before starting, make sure you have:
* An existing S-Docs Document Template
* The Document Template's **Related To Type** set to `Opportunity`
* Permission to edit S-Docs Document Templates
* At least one Opportunity with an Account and a valid contact email for testing
* Basic familiarity with Merge Field syntax
If you plan to use an org-wide sender address, make sure that address already exists in Salesforce.
{% stepper %}
{% step %}
### Open the Document Template Editor
1. Navigate to **S-Docs Templates**.
2. Open your quote Document Template.
3. Click **Edit Template**.
4. Open **Email Settings**.
You are now in the tab that controls email defaults for this Document Template.
{% endstep %}
{% step %}
### Set the Default Subject
Use a subject pattern that tells the recipient what the email contains.
1. In **Email Subject Settings**, find **Subject**.
2. Enter this value:
{% code title="Email subject" %}
```
Quote for {!Opportunity.Name} - {!Opportunity.Account.Name}
```
{% endcode %}
3. Leave **Lock Subject** unchecked.
4. Leave **Require subject line** unchecked.
The email composer now opens with a prefilled subject.
Example output: `Quote for Renewal - Acme Corporation`
{% hint style="info" %}
Use single-brace Merge Fields like `{!Opportunity.Name}` in settings tabs. Use double-brace Merge Fields like `{{!Opportunity.Name}}` in the Document Template body.
{% endhint %}
{% endstep %}
{% step %}
### Set the Default Recipients
This prevents you from entering the same email addresses repeatedly.
1. Stay in **Email Settings**.
2. In **Email Recipient Settings**, find **To**.
3. Enter this value:
{% code title="To address" %}
```
{!Opportunity.Account.BillingEmail}
```
{% endcode %}
4. Leave **Lock To** unchecked.
5. Leave **CC**, **BCC**, and **Reply To** blank.
The email composer now pulls the main recipient from the related Opportunity account.
If the source field is blank, you can still enter an address manually.
{% endstep %}
{% step %}
### Set the Sender Behavior
Choose whether the email should come from you or from one shared address.
1. In **Email Sender Settings**, find **From**.
2. Select one of these options:
* **Logged in user** for personal sending
* Your org-wide email address for shared sending
3. Leave **Restrict to Org-Wide Addresses** unchecked if you want flexibility.
4. Leave **Enable user to choose/select from a picklist** unchecked.
5. Enable **Use Salesforce Email Signature** if your team uses Salesforce signatures.
This defines who the email appears to come from and whether your signature is added.
{% endstep %}
{% step %}
### Add Sending Guardrails
Use these options when you need tighter control over outbound email.
1. Scroll to **Other Email Settings**.
2. In **Email domain restriction**, enter approved domains if needed.
{% code title="Allowed domains" %}
```
yourcompany.com,partnerdomain.com
```
{% endcode %}
3. Enable **Lock Body** to prevent email-message edits.
4. Enable **Lock Subject** if the subject must stay fixed.
These settings help keep email content consistent and reduce sending mistakes.
{% endstep %}
{% step %}
### Save and Test the Email Flow
1. Click **Save**.
2. Open a test Opportunity.
3. Generate the document with your Document Template.
4. From the generated document, click **Email**.
5. Verify these values:
* **Subject** is prefilled.
* **To** is prefilled when source data exists.
* **From** matches your selected sender option.
* Domain restrictions behave as expected.
6. Send a test email.
You now have a Document Template that opens with consistent email settings.
{% endstep %}
{% endstepper %}
After testing, confirm these results:
* The subject follows your expected pattern.
* The recipient field pulls the expected email address.
* The sender option matches your team's process.
* Locked or restricted fields behave as expected.
## Applying guardrails and limits
### Follow Merge Field Rules
* **Use** single braces in settings tabs.
* If you mix syntax or casing, values can print as raw text or stay blank.
### Configure Sender Behavior
* **Use** an org-wide address only if it is already configured in Salesforce.
* **Expect** sender choices to follow your org's available email address rules.
### Configure Recipient Behavior
* **Check** that the source email field contains real data before testing.
* **Leave** `To` unlocked if users may need to correct or replace recipients.
### Follow Testing Rules
* **Test** with an Opportunity that has real account and email data.
* **Generate** a fresh document after each email settings change.
* **Verify** subject, recipients, sender, and restrictions every time.
* If you skip testing, email issues can surface after live sends.
# Create Your First Email Template
Create an HTML email template, add merge fields, and test default email behavior from an Opportunity record.
## What You'll Learn
* Create an HTML email template for `Opportunity`
* Add merge fields to the email body
* Configure default subject, recipient, and sender settings
* Test the template with a real Salesforce record
* Troubleshoot blank recipients and raw merge field output
## What You'll Build
In this tutorial, you will build a reusable quote delivery email template for `Opportunity`.
By the end, you will have:
* An HTML template that works as the email body
* A personalized message with `Opportunity` and `Account` merge fields
* A default subject and recipient value
* A tested email flow ready for document delivery
**Estimated time:** 15 minutes
## Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates** in Salesforce
* Permission to create and edit S-Docs templates
* One test `Opportunity` with an `Account` and a valid email field
* Basic familiarity with merge fields such as `{{!Opportunity.Name}}`
If you plan to use an org-wide sender address, make sure it already exists in Salesforce.
{% stepper %}
{% step %}
### Step 1: Create the email template record
Start by creating the template record that will hold the email body and email settings.
1. Open the App Launcher.
2. Search for `S-Docs`.
3. Open **S-Docs Templates**.
4. Click **New**.
5. Set **Template Name** to a clear value, such as `Opportunity Quote Email`.
6. Set **Related To Type** to `Opportunity`.
7. Set **Template Format** to `HTML`.
8. Click **Save**.
What you just did:
* Created a template record for email content
* Tied the template to `Opportunity`
* Chose the format required for email body templates
{% endstep %}
{% step %}
### Step 2: Open the template editor
Now open the editor where you will build the body and set email defaults.
1. Open the new template record.
2. Click **Template Editor**.
You are now in the editor for the new HTML template.
{% endstep %}
{% step %}
### Step 3: Build the email body
Start with a short message that uses a few merge fields.
Add a body like this:
{% code title="Email body" %}
```html
Hello {{!Opportunity.Account.Name}},
Thank you for reviewing {{!Opportunity.Name}}.
Please find your quote attached.
If you have questions, reply to this email and we will help.
```
{% endcode %}
You can type the content directly in the editor, or insert fields from the field picker and build the message around them.
What you just did:
* Added the visible email message
* Personalized the body with record data
* Used double-brace merge fields for template body content
{% endstep %}
{% step %}
### Step 4: Set the default subject
Use a subject that tells the recipient exactly what the email contains.
1. Open **Email Settings**.
2. In **Email Subject Settings**, find **Subject**.
3. Enter this value:
{% code title="Email subject" %}
```
Quote for {!Opportunity.Name} - {!Opportunity.Account.Name}
```
{% endcode %}
4. Leave **Lock Subject** unchecked.
Example output: `Quote for Renewal - Acme Corporation`
{% hint style="info" %}
Use single-brace merge fields like `{!Opportunity.Name}` in settings tabs. Use double-brace merge fields like `{{!Opportunity.Name}}` in the template body.
{% endhint %}
What you just did:
* Added a reusable subject pattern
* Pulled record values into the subject
* Kept the subject editable for users
{% endstep %}
{% step %}
### Step 5: Set the default recipient
Now define who receives the email by default.
1. Stay in **Email Settings**.
2. In **Email Recipient Settings**, find **To**.
3. Enter the merge field for your email source.
Example:
{% code title="To address" %}
```
{!Opportunity.Account.BillingEmail}
```
{% endcode %}
{% hint style="info" %}
If the merge field does not result into a value, feel free to use your personal email address for testing.
{% endhint %}
4. Leave **Lock To** unchecked.
Use the email field that fits your process best.
If your org stores email on another related record, use that field instead.
What you just did:
* Set a default recipient for the template
* Pulled the value from the source record
* Left the field open for user review and edits
{% endstep %}
{% step %}
### Step 6: Set sender behavior and basic guardrails
Choose who the email appears to come from and apply any limits you need.
1. In **Email Sender Settings**, find **From**.
2. Select one of these options:
* `Logged in user`
* Your org-wide email address
{% endstep %}
{% step %}
### Step 7: Save and test the template
Test the base version before you add more variations.
1. Click **Save**.
2. Open a test `Opportunity`.
3. Generate a document with the template.
4. Open the email action.
5. Verify these results:
* **Subject** is prefilled
* **To** is prefilled when the source field has data
* The body shows merged record values
* **From** matches your selected sender option
Send one test email when everything looks correct.
What you just did:
* Confirmed the template works with real record data
* Verified the body, subject, and recipient behavior
* Finished one working email template before adding refinements
{% endstep %}
{% endstepper %}
## Common Issues and Solutions
The subject shows raw merge field text
Check these items:
* Use single braces in **Email Settings**, such as `{!Opportunity.Name}`
* Do not use double braces in settings tabs
* Save the template and generate a fresh test
The recipient field is blank
Check these items:
* Confirm the source email field contains data on the test record
* Confirm the field path matches the record relationship you used
* Leave **To** unlocked if users may need to type the address manually
The email body does not personalize correctly
Check these items:
* Use double braces in the body, such as `{{!Opportunity.Name}}`
* Confirm the field path is valid for the template's **Related To Type**
* Regenerate the email after each body change
The sender option I want is not available
Check these items:
* Confirm the org-wide email address already exists in Salesforce
* Confirm your user can access that sender option
* Test with `Logged in user` first if you need to isolate the issue
The template does not appear in the email workflow
Check these items:
* Confirm the template uses the correct **Related To Type**
* Confirm the template is available for the object you are testing
* Generate from a record that matches the template object
## What You've Learned
✅ Created an HTML email template for `Opportunity`\
✅ Added merge fields to the email body\
✅ Configured default subject, recipient, and sender settings\
✅ Tested the template with a real Salesforce record\
✅ Learned the most common fixes for email template issues
## Next Steps
* Use [Configure Template Settings: Email](/quick-start/template-building/customize-template-settings-email) to go deeper on sender controls, domain restrictions, and locked fields.
* Use [Generate and Email Your Document](/quick-start/getting-started/generate-and-email-your-document) to test the full end-user workflow.
* Use [Get Started with Merge Fields](/quick-start/template-building/how-to-auto-fill-customer-data-into-templates) if you want more field placement practice.
## Practice Exercise
Build a second email template for `Opportunity` that includes:
1. A subject with `Opportunity.Name`
2. A recipient pulled from a related email field
3. A short body with at least two merge fields
4. One test email sent from a real record
Bonus challenges:
* Switch the sender to an org-wide email address
* Add a domain restriction
* Lock the body after the base version works
# Create Your First Word Template
Create a Microsoft Word template, add S-Docs syntax, upload the file, and test DOCX generation.
## What You'll Learn
* Create a DOCX template record for S-Docs
* Generate Microsoft template syntax from the template editor
* Place bracketed merge fields into a Word document
* Add conditional logic and related list syntax to a DOCX file
* Upload the finished DOCX file and test generation
## What You'll Build
In this tutorial, you will build a simple Word-based quote template for `Opportunity`.
By the end, you will have:
* A DOCX template record tied to `Opportunity`
* A Word document with bracketed S-Docs merge fields
* A conditional note that appears only for one stage
* A related list pattern you can paste into a Word table
* A finished DOCX file uploaded back to S-Docs
**Estimated time:** 20 minutes
## Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates** in Salesforce
* Permission to create or edit templates
* Microsoft Word or another editor that saves valid `.docx` files
* One test `Opportunity` with an Account, Stage, and Amount
* Basic familiarity with merge fields such as `{{!Opportunity.Name}}`
{% hint style="info" %}
DOCX syntax follows the same Microsoft template pattern used by PPTX and XLSX templates.
{% endhint %}
{% stepper %}
{% step %}
### Step 1: Create the DOCX template record
Start by creating the Salesforce template record before you build the Word file.
1. Open the App Launcher.
2. Search for `S-Docs`.
3. Open **S-Docs Templates**.
4. Click **New**.
5. Set **Related To Type** to `Opportunity`.
6. Set **Template Format** to `DOCX`.
7. Enable **Enable New Microsoft Template Upload**.
8. Click **Save**.
This record gives you a place to configure settings and generate the syntax you will paste into Word.
{% endstep %}
{% step %}
### Step 2: Open the template editor and generate syntax
The template editor is your syntax builder for Microsoft templates.
1. Open the new template record.
2. Click **Template Editor**.
3. Use **Insert Field** to choose the fields you want in the document.
4. Copy each generated value from the output box.
For DOCX templates, merge fields, related lists, and conditional blocks must be enclosed in square brackets.
If you need literal bracket characters in the document, use `BRACKETOPEN` and `BRACKETCLOSE`.
{% endstep %}
{% step %}
### Step 3: Build the document body in Microsoft Word
Now create the visible document in Word.
Start with a simple quote header and summary.
Paste this pattern into your DOCX file:
{% code title="quote-summary.docx.txt" %}
```plaintext
Quote for [{{!Opportunity.Account.Name}}]
Opportunity: [{{!Opportunity.Name}}]
Stage: [{{!Opportunity.StageName}}]
Close Date: [{{!Opportunity.CloseDate}}]
Amount: [{{!Opportunity.Amount}}]
```
{% endcode %}
What you just did:
* Added basic merge fields for the base record
* Used the bracketed Microsoft template syntax
* Created a working first version before adding logic
{% endstep %}
{% step %}
### Step 4: Add one conditional block
Use conditional logic when part of the document should appear only for some records.
Add this block below the summary:
{% code title="conditional-note.docx.txt" %}
```plaintext
[]
This quote is in active review.
[]
```
{% endcode %}
What you just did:
* Added a stage-based rule to the DOCX file
* Kept the full conditional block inside bracketed Microsoft syntax
* Created one safe pattern you can reuse with other fields later
{% endstep %}
{% step %}
### Step 5: Save the DOCX file
Save the file locally before you upload it.
Use a clear file name such as `opportunity-quote-template.docx`.
After saving, reopen the file once to confirm the content and formatting still look correct.
{% endstep %}
{% step %}
### Step 6: Upload the DOCX file to the template
Upload the finished Word file back to the S-Docs template record.
If you are using S-Docs Summer 2025 (`v10.0`) or later:
1. Return to the template record.
2. Click **Upload Files**.
3. Select the `.docx` file.
If you are using an earlier version, upload the file from the template editor.
Once the upload completes, the template is ready for generation.
{% hint style="warning" %}
Microsoft templates with **Enable New Microsoft Template Upload** checked are generated through S-Docs LWCs or the SDK.
{% endhint %}
{% endstep %}
{% step %}
### Step 7: Generate a test document
Test the template with a real `Opportunity` record.
1. Open a test opportunity.
2. Generate the DOCX template.
3. Download or preview the generated file.
4. Verify the output.
Check these results:
* The account and opportunity names resolve correctly
* The stage and amount display real record values
* The conditional note appears only when the stage is `Proposal/Price Quote`
* No raw S-Docs syntax appears in the document
{% endstep %}
{% endstepper %}
## Common DOCX syntax patterns
Use the patterns below when you expand the template.
### Merge field syntax
DOCX templates require brackets around merge fields.
Use **Insert Field** in the template editor to generate the syntax.
Then:
1. Select the field.
2. Apply any formatting.
3. Copy the generated syntax.
4. Paste it into Microsoft Word.
### Related list syntax
To insert a related list into a DOCX template, generate the related list syntax and paste it into a prebuilt Word table.
Use **Insert Related List** at the top of the template editor to build the related list.
When the related list is ready:
1. Open the **Get Related List** tab in the related list menu.
2. Copy the generated source.
3. In Word, create a styling table with:
* a header row with your intended header text
* an odd row
* an even row
4. Paste the related list code into the cell in the first column under the header.
{% hint style="info" %}
The same related list placement pattern used in Microsoft PowerPoint templates also applies to DOCX.
{% endhint %}
### Conditional logic syntax
Use **Insert Conditional Logic** at the top of the template editor to open the logic builder.
Build the condition, then copy the generated output into Word.
If the rendered content contains merge fields, those merge fields must also be enclosed in brackets.
{% code title="docx-conditional-logic.txt" %}
```plaintext
[]
High-value quote
[]
```
{% endcode %}
{% hint style="warning" %}
Do not place `RENDER` tags on the same line as the `LINEITEMS` block.
{% endhint %}
### Additional syntax
#### Rich text images
To display images stored in rich text fields, use three curly braces instead of two.
{% code title="docx-rich-text-image.txt" %}
```plaintext
[{{{!Object.FieldName}}}]
```
{% endcode %}
To adjust image dimensions:
1. Open the **Document Options** tab in the template editor.
2. Scroll to **Other Options**.
3. Enter the size in **Rich Text Image Dimensions**.
#### Named queries
If you use named queries in a DOCX template, convert them to the bracketed Microsoft template syntax.
If the named query looks like this:
{% code title="named-query-standard.txt" %}
```plaintext
{{!myQuery1.fieldname}}
```
{% endcode %}
Update it to this:
{% code title="named-query-docx.txt" %}
```plaintext
[{{!
...
}}]
[{{!myQuery1.fieldname}}]
```
{% endcode %}
DOCX templates support named query `filter` and `offset`.
## Common Issues and Solutions
"The document shows raw merge field syntax"
Check these items:
* Confirm each merge field is wrapped in square brackets
* Confirm the merge field itself still uses `{{! ... }}`
* Reupload the DOCX file after fixing the syntax
"The document generates, but values are blank"
Check these items:
* Confirm the template uses **Related To Type** `Opportunity`
* Confirm the test record has values in the fields you used
* Recopy the field syntax from **Insert Field** if needed
"The conditional note never appears"
Check these items:
* Confirm both `RENDER` tags are wrapped in square brackets
* Confirm the compared value matches the record value exactly
* Test the same record value directly in the document first
"My related list formatting looks wrong"
Check these items:
* Confirm the related list code was pasted into the first cell under the header
* Confirm the Word table includes header, odd, and even rows
* Regenerate the related list syntax after query changes
"My latest DOCX changes do not show up"
Check these items:
* Save the Word file before uploading it
* Upload the newest version of the `.docx` file
* Generate a new document after each upload
"DOCX generation is not available"
Check these items:
* Enable **Enable New Microsoft Template Upload** on the template
* Confirm the template was uploaded as a `.docx` file
* Generate through an S-Docs LWC or the SDK when the new Microsoft upload flow is enabled
## What You've Learned
✅ Created a DOCX template record for `Opportunity`\
✅ Used the template editor to generate Microsoft template syntax\
✅ Added bracketed merge fields to a Word document\
✅ Added conditional logic and related list patterns\
✅ Uploaded and tested a DOCX template in S-Docs
## Next Steps
* Use [Template Attributes Tutorial](/quick-start/template-building/how-to-format-text-dates-and-currency) to format values inside the document.
* Use [Getting Started with Conditional Logic](/quick-start/template-building/conditional-logic-tutorial) to add more conditions.
* Use [Creating Your First Named Query](/quick-start/template-building/creating-your-first-named-query-tutorial) to reuse query results in Microsoft templates.
* Use [Build and Upload a PPTX Template](/quick-start/template-building/build-and-upload-a-pptx-template) if you also build PowerPoint templates.
* Use [Add S-Docs Lightning Components to a Record Page](/quick-start/document-generation/add-s-docs-lightning-components-to-a-record-page) to expose the template for record-page generation.
## Practice Exercise
Build a second DOCX template for `Opportunity` that includes:
1. A title with `Opportunity.Name`
2. A customer line with `Opportunity.Account.Name`
3. A stage-based conditional note
4. A related list placeholder in a Word table
5. One test generation from a real record
Bonus challenges:
* Add one more merge field from a related record
* Add a named query to the DOCX file
* Rebuild the same pattern for `Account`
# Create Your First PowerPoint Template
Create a Microsoft PowerPoint template, add S-Docs syntax, upload the file, and test PPTX generation.
## What You'll Learn
* Create a PPTX template record for S-Docs
* Generate Microsoft template syntax from the template editor
* Place bracketed merge fields into a PowerPoint presentation
* Add conditional logic and related list syntax to a PPTX file
* Upload the finished PPTX file and test generation
## What You'll Build
In this tutorial, you will build a simple PowerPoint-based quote template for `Opportunity`.
By the end, you will have:
* A PPTX template record tied to `Opportunity`
* A PowerPoint presentation with bracketed S-Docs merge fields
* A conditional note that appears only for one stage
* A related list pattern you can paste into a PowerPoint table
* A finished PPTX file uploaded back to S-Docs
**Estimated time:** 20 minutes
## Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates** in Salesforce
* Permission to create or edit templates
* Microsoft PowerPoint or another editor that saves valid `.pptx` files
* One test `Opportunity` with an Account, Stage, and Amount
* Basic familiarity with merge fields such as `{{!Opportunity.Name}}`
{% hint style="info" %}
PPTX syntax follows the same Microsoft template pattern used by DOCX and XLSX templates.
{% endhint %}
{% stepper %}
{% step %}
### Step 1: Create the PPTX template record
Start by creating the Salesforce template record before you build the PowerPoint file.
1. Open the App Launcher.
2. Search for `S-Docs`.
3. Open **S-Docs Templates**.
4. Click **New**.
5. Set **Related To Type** to `Opportunity`.
6. Set **Template Format** to `PPTX`.
7. Enable **Enable New Microsoft Template Upload**.
8. Click **Save**.
This record gives you a place to configure settings and generate the syntax you will paste into PowerPoint.
{% endstep %}
{% step %}
### Step 2: Open the template editor and generate syntax
The template editor is your syntax builder for Microsoft templates.
1. Open the new template record.
2. Click **Template Editor**.
3. Use **Insert Field** to choose the fields you want in the presentation.
4. Copy each generated value from the output box.
For PPTX templates, merge fields, related lists, and conditional blocks must be enclosed in square brackets.
If you need literal bracket characters in the presentation, use `BRACKETOPEN` and `BRACKETCLOSE`.
{% endstep %}
{% step %}
### Step 3: Build the presentation body in Microsoft PowerPoint
Now create the visible presentation in PowerPoint.
Start with a simple quote title and summary slide.
Paste this pattern into your PPTX file:
{% code title="quote-summary.pptx.txt" %}
```plaintext
Quote for [{{!Opportunity.Account.Name}}]
Opportunity: [{{!Opportunity.Name}}]
Stage: [{{!Opportunity.StageName}}]
Close Date: [{{!Opportunity.CloseDate}}]
Amount: [{{!Opportunity.Amount}}]
```
{% endcode %}
What you just did:
* Added basic merge fields for the base record
* Used the bracketed Microsoft template syntax
* Created a working first version before adding logic
{% endstep %}
{% step %}
### Step 4: Add one conditional block
Use conditional logic when part of the presentation should appear only for some records.
Add this block below the summary:
{% code title="conditional-note.pptx.txt" %}
```plaintext
[]
This quote is in active review.
[]
```
{% endcode %}
What you just did:
* Added a stage-based rule to the PPTX file
* Kept the full conditional block inside bracketed Microsoft syntax
* Created one safe pattern you can reuse with other fields later
{% endstep %}
{% step %}
### Step 5: Save the PPTX file
Save the file locally before you upload it.
Use a clear file name such as `opportunity-quote-template.pptx`.
After saving, reopen the file once to confirm the content and formatting still look correct.
{% endstep %}
{% step %}
### Step 6: Upload the PPTX file to the template
Upload the finished PowerPoint file back to the S-Docs template record.
If you are using S-Docs Summer 2025 (`v10.0`) or later:
1. Return to the template record.
2. Click **Upload Files**.
3. Select the `.pptx` file.
If you are using an earlier version, upload the file from the template editor.
Once the upload completes, the template is ready for generation.
{% hint style="warning" %}
PPTX templates with **Enable New Microsoft Template Upload** checked are not compatible with legacy custom button generation.
They can only be generated through S-Docs LWCs or the SDK.
{% endhint %}
{% endstep %}
{% step %}
### Step 7: Generate a test document
Test the template with a real `Opportunity` record.
1. Open a test opportunity.
2. Generate the PPTX template.
3. Download or preview the generated file.
4. Verify the output.
Check these results:
* The account and opportunity names resolve correctly
* The stage and amount display real record values
* The conditional note appears only when the stage is `Proposal/Price Quote`
* No raw S-Docs syntax appears in the presentation
{% endstep %}
{% endstepper %}
## Common PPTX syntax patterns
Use the patterns below when you expand the template.
### Merge field syntax
PPTX templates require brackets around merge fields.
Use **Insert Field** in the template editor to generate the syntax.
Then:
1. Select the field.
2. Apply any formatting.
3. Copy the generated syntax.
4. Paste it into Microsoft PowerPoint.
### Related list syntax
To insert a related list into a PPTX template, generate the related list syntax and paste it into a prebuilt PowerPoint table.
Use **Insert Related List** at the top of the template editor to build the related list.
When the related list is ready:
1. Open the **Get Related List** tab in the related list menu.
2. Copy the generated source.
3. In PowerPoint, create a styling table with:
* a header row with your intended header text
* an odd row
* an even row
4. Paste the related list code into the cell in the first column under the header.
{% hint style="info" %}
The same related list placement pattern used in Microsoft Word templates also applies to PPTX.
{% endhint %}
### Conditional logic syntax
Use **Insert Conditional Logic** at the top of the template editor to open the logic builder.
Build the condition, then copy the generated output into PowerPoint.
If the rendered content contains merge fields, those merge fields must also be enclosed in brackets.
{% code title="pptx-conditional-logic.txt" %}
```plaintext
[]
High-value quote
[]
```
{% endcode %}
{% hint style="warning" %}
Do not place `RENDER` tags on the same line as the `LINEITEMS` block.
{% endhint %}
### Additional syntax
#### Rich text images
To display images stored in rich text fields, use three curly braces instead of two.
{% code title="pptx-rich-text-image.txt" %}
```plaintext
[{{{!Object.FieldName}}}]
```
{% endcode %}
To adjust image dimensions:
1. Open the **Document Options** tab in the template editor.
2. Scroll to **Other Options**.
3. Enter the size in **Rich Text Image Dimensions**.
{% hint style="info" %}
This setting controls the size of all images merged into the PPTX template from rich text fields.
{% endhint %}
#### Named queries
If you use named queries in a PPTX template, convert them to the bracketed Microsoft template syntax.
If the named query looks like this:
{% code title="named-query-standard.txt" %}
```plaintext
{{!myQuery1.fieldname}}
```
{% endcode %}
Update it to this:
{% code title="named-query-pptx.txt" %}
```plaintext
[{{!
...
}}]
[{{!myQuery1.fieldname}}]
```
{% endcode %}
PPTX templates support named query `filter` and `offset`.
## Common Issues and Solutions
"The presentation shows raw merge field syntax"
Check these items:
* Confirm each merge field is wrapped in square brackets
* Confirm the merge field itself still uses `{{! ... }}`
* Reupload the PPTX file after fixing the syntax
"The presentation generates, but values are blank"
Check these items:
* Confirm the template uses **Related To Type** `Opportunity`
* Confirm the test record has values in the fields you used
* Recopy the field syntax from **Insert Field** if needed
"The conditional note never appears"
Check these items:
* Confirm both `RENDER` tags are wrapped in square brackets
* Confirm the compared value matches the record value exactly
* Test the same record value directly in the presentation first
"My related list formatting looks wrong"
Check these items:
* Confirm the related list code was pasted into the first cell under the header
* Confirm the PowerPoint table includes header, odd, and even rows
* Regenerate the related list syntax after query changes
"My latest PPTX changes do not show up"
Check these items:
* Save the PowerPoint file before uploading it
* Upload the newest version of the `.pptx` file
* Generate a new document after each upload
"PPTX generation is not available"
Check these items:
* Enable **Enable New Microsoft Template Upload** on the template
* Confirm the template was uploaded as a `.pptx` file
* Generate through an S-Docs LWC or the SDK when the new Microsoft upload flow is enabled
## What You've Learned
✅ Created a PPTX template record for `Opportunity`\
✅ Used the template editor to generate Microsoft template syntax\
✅ Added bracketed merge fields to a PowerPoint presentation\
✅ Added conditional logic and related list patterns\
✅ Uploaded and tested a PPTX template in S-Docs
## Next Steps
* Use [Template Attributes Tutorial](/quick-start/template-building/how-to-format-text-dates-and-currency) to format values inside the presentation.
* Use [Getting Started with Conditional Logic](/quick-start/template-building/conditional-logic-tutorial) to add more conditions.
* Use [Creating Your First Named Query](/quick-start/template-building/creating-your-first-named-query-tutorial) to reuse query results in Microsoft templates.
* Use [Build and Upload a DOCX Template](/quick-start/template-building/create-your-first-word-template) if you also build Word templates.
* Use [Add S-Docs Lightning Components to a Record Page](/quick-start/document-generation/add-s-docs-lightning-components-to-a-record-page) to expose the template for record-page generation.
## Practice Exercise
Build a second PPTX template for `Opportunity` that includes:
1. A title with `Opportunity.Name`
2. A customer line with `Opportunity.Account.Name`
3. A stage-based conditional note
4. A related list placeholder in a PowerPoint table
5. One test generation from a real record
Bonus challenges:
* Add one more merge field from a related record
* Add a named query to the PPTX file
* Rebuild the same pattern for `Account`
# How to Format Text, Dates, and Currency
Format dates, numbers, checkboxes, and uppercase billing output with merge field attributes.
Use this tutorial when you want one template to control how values render in the document body.
## What it looks like
After setup, one generated invoice gives the user all of this:
* A readable invoice date, such as `April 9, 2026`
* A formatted amount, such as `$4,222,300.80`
* Checkbox icons for payment options
* An uppercase billing block for customer details
* Reusable merge field patterns you can copy into other templates
This is the right end state for invoice, quote, and order templates that need clean output without changing the source data.
## When to use template attributes
Use template attributes when you need to change how a field renders inside the template body.
**Best for:**
* Formatting dates and numbers for business documents
* Showing checkbox or radio output from boolean fields
* Transforming text case without changing Salesforce data
* Reusing the same merge field pattern across similar fields
Use another feature when the problem is different:
* Use [Configure Document Generation Template Settings](/quick-start/template-building/customize-template-settings-document-generation) when you need file naming, save behavior, or page layout.
* Use [Getting Started with Conditional Logic](/quick-start/template-building/conditional-logic-tutorial) when content should appear only when conditions pass.
* Use [Get Started with Calculations](/quick-start/template-building/get-started-with-calculations) when you need derived values such as deposits, tax, or due dates.
* Use [Adding Tables (Like Products or Contacts) to Your Document](/quick-start/template-building/adding-tables-like-products-or-contacts-to-your-document) when you need child records or table output.
## Build an invoice template with template attributes
### What you'll configure
* Basic merge field structure
* `format-date` for invoice date
* `format-number` for currency values
* `checkbox` for payment options
* `ToUpperCase` for billing fields
**Estimated time:** 20 minutes
### Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates**
* Permission to create or edit templates
* An S-Docs template related to `Opportunity`
* A test Opportunity with an Amount, Close Date, and Account
* Basic familiarity with merge fields such as `{{!Opportunity.Name}}`
If you are brand new to S-Docs syntax, start with a basic merge field tutorial first.
{% stepper %}
{% step %}
### Step 1: Open or create the template
Start with an Opportunity template that will generate an invoice.
1. Go to **S-Docs Templates** in Salesforce.
2. Open an existing template or click **New Template**.
3. Set **Related To Type** to `Opportunity`.
4. Set **Template Format** to `PDF`.
5. Open the template editor.
You now have a place to add template attributes in the document body.
{% endstep %}
{% step %}
### Step 2: Start with plain merge fields
Start with raw values first. This makes the attribute changes obvious.
Add this near the top of the template:
{% code title="invoice-baseline.html" %}
```html
Invoice
Opportunity: {{!Opportunity.Name}}
Invoice Date: {{!Opportunity.CloseDate}}
Amount Due: {{!Opportunity.Amount}}
```
{% endcode %}
What you just did:
* Added three plain merge fields with no attributes
* Confirmed the base object and field paths are correct
* Created a before state for the next formatting steps
How to read the syntax:
* `{{!` starts the merge field
* `Opportunity.CloseDate` points to one field on the base record
* Attributes come after the field path
* `}}` closes the merge field
{% endstep %}
{% step %}
### Step 3: Add a formatted invoice date
A date attribute turns raw Salesforce date output into invoice-ready text.
Add this near the top of the template:
{% code title="invoice-header.html" %}
```html
```
{% endcode %}
What you just did:
* Applied `format-date` to `Opportunity.CloseDate`
* Used `MMMM d, yyyy` for month name, day, and four-digit year
* Created a readable invoice header without changing the source field
Why this pattern matters:
* The field path stays the same
* Only the attribute changes the output
* You can reuse this pattern on any date field
{% endstep %}
{% step %}
### Step 4: Format the invoice amount
A number attribute lets you keep raw numeric data in Salesforce while showing clean currency in the document.
Add this below the date:
{% code title="invoice-total.html" %}
```html
```
{% endcode %}
What you just did:
* Applied `format-number` to the amount field
* Added commas and two decimal places with `#,###.##`
* Kept the dollar sign outside the attribute for predictable output
Pattern to remember:
* Start with the raw field: `{{!Opportunity.Amount}}`
* Add one space
* Add the attribute: `format-number="#,###.##"`
* Keep visible text, such as `$`, outside the merge field
{% endstep %}
{% step %}
### Step 5: Add payment method checkboxes
Use checkbox attributes when the source field is a true Salesforce checkbox field.
If these fields do not exist yet, create `Payment_by_Check__c` and `Payment_by_Credit_Card__c` on `Opportunity` before continuing.
Then add this block:
{% code title="payment-methods.html" %}
```html
```
{% endcode %}
What you just did:
* Rendered boolean fields as checkbox icons instead of `true` or `false`
* Kept the labels readable for the final document
* Used a pattern you can swap to `checkbox="black"` or `checkbox="radio"` later
Merge field rule:
* Put the label outside the merge field
* Keep the `checkbox` attribute inside the same field
{% endstep %}
{% step %}
### Step 6: Add an uppercase billing block
Text attributes are useful when the document needs a formal display style.
Add this below the invoice header or near the customer section:
{% code title="billing-block.html" %}
```html
Bill To:
{{!Opportunity.Account.Name ToUpperCase="true"}}
{{!Opportunity.Account.BillingStreet ToUpperCase="true"}}
{{!Opportunity.Account.BillingCity ToUpperCase="true"}},
{{!Opportunity.Account.BillingState ToUpperCase="true"}}
{{!Opportunity.Account.BillingPostalCode}}
```
{% endcode %}
What you just did:
* Converted account name and address lines to uppercase in the output only
* Left the postal code unchanged
* Applied the same attribute pattern across several related fields
Pattern to remember:
* Keep each field separate
* Repeat the same attribute on each line you want transformed
* Leave fields unchanged when you want their original display
{% endstep %}
{% step %}
### Step 7: Test a few merge field variations
Once the base version works, swap one pattern at a time.
Try one of these date alternatives:
{% code title="date-variations.html" %}
```html
{{!Opportunity.CloseDate format-date="MM/dd/yyyy"}}
{{!Opportunity.CloseDate format-date="dd.MM.yyyy"}}
{{!Opportunity.CloseDate format-date="EEEE, MMMM d, yyyy"}}
```
{% endcode %}
Try one of these number alternatives:
{% code title="number-variations.html" %}
```html
${{!Opportunity.Amount format-number="#,###"}}
€{{!Opportunity.Amount format-number="#.###,##"}}
£{{!Opportunity.Amount format-number="#,###.00"}}
```
{% endcode %}
What you just did:
* Reused the same merge field with different attributes
* Changed output without changing the Salesforce data
* Built patterns you can copy into quote or order templates
{% endstep %}
{% step %}
### Step 8: Save and test the template
Generate the invoice from a real Opportunity before adding variations.
1. Click **Save** in the template editor.
2. Open a test Opportunity with the fields you used.
3. Generate the template.
4. Verify the output.
Check these results:
* The invoice date uses a readable format
* The amount shows commas and decimals
* The payment fields render as checkboxes
* The billing block appears in uppercase
* The raw merge fields no longer appear in their default Salesforce format
{% endstep %}
{% endstepper %}
## Guardrails and limits
### Merge field syntax rules
* **Always** start with `{{!` and end with `}}`.
* **Always** keep attributes inside the same merge field.
* **Always** leave a space between the field name and the first attribute.
* **Always** keep markup outside the merge field.
* If markup breaks the merge field, S-Docs prints the syntax as literal text.
### Date and number formatting rules
* **Use** lowercase `yyyy` for the year in `format-date` patterns.
* **Type** currency symbols outside `format-number`.
* If the pattern is wrong, values can render in an unexpected format or stay unformatted.
### Checkbox and output limits
* **Use** `checkbox` only with boolean fields.
* **Expect** checkbox rendering to work best in PDF templates.
* If you apply `checkbox` to the wrong field type, the document can show raw values instead of icons.
### Testing rules
* **Generate** one test document after each major syntax change.
* **Use** a record with real values and known checkbox states.
* If you skip testing, syntax problems usually surface only in final output.
# How to Show or Hide Content Automatically
Show or hide template sections with field checks, blank-value rules, and multi-part conditions.
Use this tutorial when one template must generate different output for different records.
## What it looks like
After setup, one quote can produce all of this:
* A VIP message only for high-value customers
* A phone line only when `Contact.Phone` has a value
* A California clause only for active contracts
* A finance compliance note only for matching industries
* Reusable rule patterns for other templates
This works well for quotes, contracts, and renewal documents.
## When to use conditional logic
Use conditional logic when content should appear only when record data passes a rule.
**Best for:**
* Hiding empty labels and optional sections
* Showing regional or industry-specific clauses
* Reusing one template across several customer scenarios
Use another feature when the job is different:
* Use [Template Attributes Tutorial](/quick-start/template-building/how-to-format-text-dates-and-currency) when you need formatting only.
* Use [Get Started with Calculations](/quick-start/template-building/get-started-with-calculations) when you need thresholds or derived values.
* Use [Creating Your First Named Query](/quick-start/template-building/creating-your-first-named-query-tutorial) when you need reusable query output.
## Build a quote template with conditional logic
### What you'll configure
* A basic `RENDER` block
* Empty-field checks with `!= 'NULL'`
* Multi-part rules with `&&` and `||`
* Keyword matching with `CONTAINS`
* A quick test plan for validating output
**Estimated time:** 20 minutes
### Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates**
* Permission to create or edit templates
* An S-Docs template related to `Account`, `Contact`, or `Opportunity`
* Test records with known field values
* Basic familiarity with merge fields such as `{{!Account.Name}}`
If you are brand new to S-Docs syntax, start with a merge field tutorial first.
{% stepper %}
{% step %}
### Step 1: Open or create the template
Start with a template that should change by record data.
1. Go to **S-Docs Templates** in Salesforce.
2. Open an existing template or click **New Template**.
3. Set the correct base object.
4. Open the template editor.
5. Click **Source** if you want to paste syntax directly.
You now have a place to add conditional blocks.
{% endstep %}
{% step %}
### Step 2: Add a simple equality check
Start with one short block. This confirms the syntax works before you add more logic.
Add this where the VIP note should appear:
{% code title="vip-message.html" %}
```html
VIP customer: Thank you for your continued business.
```
{% endcode %}
What you just did:
* Compared `Account.Customer_Type__c` to one exact text value
* Used `==` for an equality check
* Rendered the paragraph only when the condition passes
How to read the syntax:
* `{{!Account.Customer_Type__c}}` is the field being checked
* `==` means the value must match exactly
* `'High Value'` is the required text
{% endstep %}
{% step %}
### Step 3: Hide a blank phone line
Use a null check when the label and value should appear together.
Add this block in the contact section:
{% code title="phone-line.html" %}
```html
Phone: {{!Contact.Phone}}
```
{% endcode %}
What you just did:
* Used `!=` for a not-equal check
* Compared the field to `NULL`
* Prevented an empty `Phone:` label from printing
This pattern works well for phone, email, title, and address lines.
{% endstep %}
{% step %}
### Step 4: Require two conditions with AND
Use AND logic when both checks must pass before showing content.
Add this clause below the customer summary:
{% code title="regional-clause.html" %}
```html
Include the California active-contract clause in this quote.
```
{% endcode %}
What you just did:
* Used `&&` for AND logic
* Grouped both checks with parentheses
* Rendered the clause only when both values match
Read the condition in order:
* `BillingState` must equal `CA`
* `Active_Contract__c` must equal `True`
* `&&` means both statements must be true
{% endstep %}
{% step %}
### Step 5: Match either value with OR
Use OR logic when one of several values should show the same content.
Add this example:
{% code title="west-coast-note.html" %}
```html
Apply the West Coast delivery language.
```
{% endcode %}
What you just did:
* Used `||` for OR logic
* Allowed either state to trigger the note
* Reused the same field in two checks
Use this pattern for state groups, segment groups, or status groups.
{% endstep %}
{% step %}
### Step 6: Match a keyword with CONTAINS
Use `CONTAINS` when the source text can vary.
Add this block in the compliance section:
{% code title="industry-keyword.html" %}
```html
Include the finance compliance checklist with this document.
```
{% endcode %}
What you just did:
* Searched within the full field value
* Matched text like `Finance Team` or `Global Finance`
* Avoided relying on one exact field value
If you need the inverse, use `NOT CONTAINS`.
{% endstep %}
{% step %}
### Step 7: Save and test the output
Test one rule at a time before combining more patterns.
1. Click **Save** in the template editor.
2. Generate the template from a record that should pass one rule.
3. Generate it again from a record that should fail.
4. Compare the output blocks.
Verify these results:
* The VIP note shows only for high-value customers
* The phone line shows only when `Contact.Phone` is populated
* The California clause shows only when both checks pass
* The finance note shows only when the keyword exists
{% endstep %}
{% endstepper %}
### Try these variations
Use these once the base version works.
An amount threshold:
{% code title="amount-threshold.html" %}
```html
```
{% endcode %}
A combined customer and industry check:
{% code title="combined-condition.html" %}
```html
Apply the customer finance compliance clause.
```
{% endcode %}
## Guardrails and limits
### Syntax rules
* **Always** close each block with ``.
* **Always** keep the full label and value inside the same block.
* **Always** use exact field API names.
* If you miss the closing tag, later content can disappear.
### Operator rules
* **Use** `==` for exact matches.
* **Use** `!= 'NULL'` for blank-value checks.
* **Wrap** multi-part conditions in parentheses.
* If the operator is wrong, the block stays hidden.
### Text-matching rules
* **Match** text values exactly when you use `==`.
* **Use** `CONTAINS` when field values vary.
* **Check** capitalization and spacing in test data.
* If the value differs, S-Docs skips the block.
### Testing rules
* **Generate** one document after each major syntax change.
* **Test** one condition alone before combining conditions.
* **Use** records that clearly pass and fail each rule.
* If you skip this, debugging gets much slower.
# Advanced Data Pulling (For Admins)
Define a named query once, then reuse the returned values anywhere in your template.
## What You'll Learn
In this tutorial, you'll build a simple quote summary that pulls one reusable result from a SOQL query. By the end, you'll know how to:
* Create a named query with ``
* Return data without rendering a table
* Reuse query results with `{{!QueryName.FieldName}}`
* Control which row is returned with `WHERE`, `ORDER BY`, and `LIMIT`
* Test and troubleshoot blank named query output
## What You'll Build
An Opportunity template that includes:
* The highest-value line item name
* The quantity for that line item
* The total price for that line item
* Reusable values you can place in the body, header, or footer
**Estimated time:** 20 minutes
## Prerequisites
Before starting, ensure you have:
* Access to S-Docs Templates in Salesforce
* Permission to create or edit templates
* An S-Docs template related to `Opportunity`
* At least one `OpportunityLineItem` record on your test opportunity
* Basic familiarity with merge fields such as `{{!Opportunity.Name}}`
If you are brand new to S-Docs syntax, complete a basic merge field tutorial first.
{% stepper %}
{% step %}
**Step 1: Open or Create Your Template**
Start with an Opportunity template where you want to show data outside a table.
1. Navigate to **S-Docs Templates** in Salesforce
2. Open an existing template or click **New Template**
3. Choose `Opportunity` as the related object
4. Open the template editor
5. Click **Source** if you want to paste the query directly
You now have a place to add a named query.
{% endstep %}
{% step %}
**Step 2: Add Your First Named Query Block**
Named queries use a SOQL block plus a reusable query name.
Add this block near the top of your template:
```xml
```
What you just did:
* Used `none` to stop S-Docs from rendering a table
* Used `TopLineItem` to store the result under one name
* Used `` to return one line item for the current opportunity
How to read it:
* `WHERE OpportunityId = '{{!Opportunity.Id}}'` ties the query to the current record
* `ORDER BY TotalPrice DESC` sorts the largest line item first
* `LIMIT 1` returns only that first row
{% hint style="warning" %}
The query name is case-sensitive.
Use the exact same value later in your merge fields.
{% endhint %}
{% endstep %}
{% step %}
**Step 3: Reuse the Returned Values**
Now place merge fields anywhere below the query block.
```plaintext
Top line item: {{!TopLineItem.Name}}
Quantity: {{!TopLineItem.Quantity}}
Total: ${{!TopLineItem.TotalPrice #,###.00}}
```
What you just did:
* Referenced the named query with `TopLineItem`
* Pulled field values from the query result
* Formatted the total as currency
The merge field pattern is:
`{{!QueryName.FieldName}}`
If the query name or field name does not match, the output will be blank.
{% endstep %}
{% step %}
**Step 4: Understand What Makes the Output Work**
Named queries only expose fields that you include in the `SELECT` clause.
In this example:
* `TopLineItem` comes from ``
* `Name`, `Quantity`, and `TotalPrice` come from `SELECT`
* The query block must appear before the merge fields that use it
If you want to output another field later, add it to the query first.
Example:
```xml
SELECT Name, Quantity, TotalPrice, UnitPrice
```
Then you can use:
```plaintext
Unit price: ${{!TopLineItem.UnitPrice #,###.00}}
```
{% endstep %}
{% step %}
**Step 5: Change Which Record the Query Returns**
Named queries are useful because you control exactly which row is stored.
Try this variation if you want the lowest-priced line item instead:
```xml
```
What changed:
* `ORDER BY TotalPrice ASC` sorts from smallest to largest
* `LowestLineItem` creates a second reusable query result
Use `WHERE`, `ORDER BY`, and `LIMIT` together when you need one specific row.
{% endstep %}
{% step %}
**Step 6: Use the Same Query Result in Multiple Places**
Once a named query runs, you can reuse it anywhere later in the template.
Example:
```html
Quote Summary
Top line item: {{!TopLineItem.Name}}
Quantity: {{!TopLineItem.Quantity}}
Total: ${{!TopLineItem.TotalPrice #,###.00}}
This quote is led by {{!TopLineItem.Name}}.
```
What you just did:
* Ran the SOQL once
* Reused the same values several times
* Kept the template shorter and easier to maintain
This is the main reason to use named queries instead of repeating logic.
{% endstep %}
{% step %}
**Step 7: Save and Test Your Template**
Now test the query with a real opportunity.
1. Click **Save** in the template editor
2. Generate the template from an opportunity with line items
3. Confirm the highest-value line item appears
4. Compare the output against the actual line items on the opportunity
What to verify:
* The template runs from `Opportunity`
* The opportunity has at least one line item
* The query includes every field you reference later
* The query name matches your merge fields exactly
{% endstep %}
{% step %}
**Step 8: Experiment with Variations**
Once the basics work, try a few common variations.
**Variation 1: Return a relationship field**
```xml
SELECT PricebookEntry.Product2.Name, Quantity, TotalPrice
FROM OpportunityLineItem
WHERE OpportunityId = '{{!Opportunity.Id}}'
ORDER BY TotalPrice DESC
LIMIT 1
```
Then output:
```plaintext
Product: {{!TopLineItem.PricebookEntry.Product2.Name}}
```
**Variation 2: Filter to a smaller set of rows**
```xml
SELECT Name, Quantity, TotalPrice
FROM OpportunityLineItem
WHERE OpportunityId = '{{!Opportunity.Id}}'
AND Quantity > 1
ORDER BY TotalPrice DESC
LIMIT 1
```
**Variation 3: Add another field to the same query**
```xml
SELECT Name, Quantity, TotalPrice, ServiceDate
FROM OpportunityLineItem
WHERE OpportunityId = '{{!Opportunity.Id}}'
ORDER BY TotalPrice DESC
LIMIT 1
```
Then output:
```plaintext
Service date: {{!TopLineItem.ServiceDate}}
```
Try one variation at a time, then regenerate the document to confirm the result.
{% endstep %}
{% endstepper %}
## Common Issues and Solutions
Issue 1: "The merge fields are blank"
Problem: The named query block runs, but the output fields do not show values.
Solution:
* Verify the query actually returns a row for the current record
* Check that the query name matches exactly, including capitalization
* Confirm every referenced field is included in the `SELECT` clause
* Make sure the merge fields appear below the named query block
Issue 2: "A table shows up instead of plain text"
Problem: The query output renders like a related list.
Solution:
* Make sure the block uses `none`
* Check that you did not replace it with a table class name
* Regenerate the document after saving the change
Issue 3: "The wrong row is returned"
Problem: You expected one record, but a different row appears.
Solution:
* Review the `WHERE` clause first
* Check the `ORDER BY` direction, `ASC` or `DESC`
* Use `LIMIT 1` when you only want one row
* Test the SOQL logic against real record data
Issue 4: "A relationship field is blank"
Problem: A field like product name does not show in the output.
Solution:
* Include the full relationship path in `SELECT`
* Use the same full path in the merge field
* Verify the related record actually exists on that row
Issue 5: "The query works in one place but not another"
Problem: Some references resolve, but earlier ones do not.
Solution:
* Place the named query before every section that uses it
* Avoid referencing the query result above the query block
* Keep the query block near the top of the template when possible
## What You've Learned
Congratulations! You've built a template with a reusable named query and learned:
✅ How to create a named query with ``\
✅ How to prevent table output with `none`\
✅ How to reuse query values with `{{!QueryName.FieldName}}`\
✅ How to control the returned row with `WHERE`, `ORDER BY`, and `LIMIT`\
✅ How to test and troubleshoot blank output
## Next Steps
Now that you've mastered the basics, you can:
### Expand Your Queries
* Pull relationship fields into your output
* Return a different row with sorting and filters
* Add more fields to one reusable query
* Build multiple named queries in one template
### Combine with Other Features
* Use named queries with conditional logic
* Pair named queries with calculations
* Reuse named query output inside component templates
* Mix named queries with standard merge fields
### Practice More
* Build a quote summary for the top-priced line item
* Show a service date only for the returned line item
* Add a second named query for a different product row
**Recommended reading:**
* Named Query Working Examples
* How to: Advanced Data Retrieval with Named Queries
* Named Query Structure
* Named Queries In Microsoft Templates (DOCX, PPTX, XLSX)
## Practice Exercise
To reinforce what you've learned, build an Opportunity template that includes:
1. A named query for the highest-value `OpportunityLineItem`
2. The line item name, quantity, and total price in plain text
3. One repeated use of the same query result in a second section
4. A variation that returns the lowest-priced line item instead
5. A test using one opportunity that has line items and one that does not
Bonus challenges:
* Add a relationship field such as `PricebookEntry.Product2.Name`
* Add another field to the same query and output it later
* Create a second named query with a different filter
# Adding Tables (Like Products or Contacts) to Your Document
Build a simple related-record table pattern you can adapt to many S-Docs templates.
### Example output
Your finished document can look like this:
| Opportunity | Stage | Close Date | Amount |
| --------------------- | -------------------- | ---------- | -----: |
| Renewal - Northwind | Proposal/Price Quote | 2026-05-15 | 25000 |
| Expansion - Northwind | Negotiation/Review | 2026-06-01 | 40000 |
| Services Add-On | Qualification | 2026-06-20 | 12000 |
## What You'll Learn
* Build a related list table from a parent record
* Query `Opportunity` records from an `Account` template
* Match table headers to `` tags in the right order
* Test the output before adding filters
* Reuse the same pattern with other object pairs
## What You'll Build
In this tutorial, you will build an account pipeline summary that lists related opportunities in a table.
This walkthrough uses `Account` as the base object and `Opportunity` as the child object.
The finished template will include:
* An account summary header
* A four-column opportunity table
* A related list query tied to the current account
* One safe variation that only shows open opportunities
**Estimated time:** 15 minutes
## Prerequisites
Before you start, make sure you have:
* Access to **S-Docs Templates** in Salesforce
* Permission to create or edit templates
* A template related to `Account`
* A test account with at least two related `Opportunity` records
* Basic familiarity with merge fields such as `{{!Account.Name}}`
If you want a shorter intro first, use [Insert Data Tables](/sdocs/advanced-template-logic/related-lists).
{% stepper %}
{% step %}
### Step 1: Open or create the template
Start with an `Account` template so the query can use the current account ID.
1. Go to **S-Docs Templates**.
2. Open an existing template or click **New Template**.
3. Set **Related To Type** to `Account`.
4. Open the template editor.
You now have a base template that can query child records from the current account.
{% endstep %}
{% step %}
### Step 2: Add the account summary header
Add a small header first.
This confirms your base merge fields resolve before you add the related list.
{% code title="account-summary-header.html" %}
```html
Account opportunity summary
Account: {{!Account.Name}}
Owner: {{!Account.Owner.Name}}
```
{% endcode %}
What you just did:
* Confirmed the template runs from `Account`
* Added visible fields to test the base record context
* Created a simple header above the opportunity table
{% endstep %}
{% step %}
### Step 3: Add the table shell
Create the visible table structure first.
Then place the query block inside the table body.
{% code title="opportunity-table-shell.html" %}
```html
Opportunity
Stage
Close Date
Amount
```
{% endcode %}
What you just did:
* Defined the columns the reader will see
* Left space for the related list query
* Created a reusable table layout for child records
{% endstep %}
{% step %}
### Step 4: Add the related list block
This example uses `Opportunity` as the child object.
It pulls records related to the current `Account`.
{% code title="account-opportunity-related-list.xml" %}
```xml
Opportunity
Stage
Close Date
Amount
```
{% endcode %}
What this does:
* Queries `Opportunity` records for the current account
* Ties the query to the base record with `WHERE AccountId = '{{!Account.Id}}'`
* Sorts the rows by `CloseDate`
* Prints one field per `` tag
How to read the block:
* `` starts the related list query
* `` controls the output style
* `` defines which child rows to return
* Each `` prints one value in the row
{% endstep %}
{% step %}
### Step 5: Match the headers and columns
The table only works cleanly when the header order matches the `` order.
In this example:
* `Opportunity` maps to `Name`
* `Stage` maps to `StageName`
* `Close Date` maps to `CloseDate`
* `Amount` maps to `Amount`
Rules to follow:
* Every displayed value needs a matching `` tag
* Every `` value must appear in the `SELECT` clause
* The first header must match the first ``
If the order does not match, the wrong values appear under the wrong headers.
{% endstep %}
{% step %}
### Step 6: Save and test the template
Test the base version before you add any variations.
1. Click **Save**.
2. Open a test account with related opportunities.
3. Generate the document.
4. Compare the document rows with the related records in Salesforce.
Verify these results:
* The header shows the expected account
* The table shows one row per related opportunity
* The rows belong to the current account only
* The values appear under the correct headers
Once this works, you have a reusable starting pattern.
{% endstep %}
{% step %}
### Step 7: Try one simple variation
Now add one safe filter.
This version only returns open opportunities.
{% code title="filtered-account-opportunity-related-list.xml" %}
```xml
table1
SELECT Name, StageName, CloseDate, Amount
FROM Opportunity
WHERE AccountId = '{{!Account.Id}}'
AND IsClosed = false
ORDER BY CloseDate ASC
NameStageNameCloseDateAmount
```
{% endcode %}
What changed:
* Added `AND IsClosed = false`
* Kept the same table structure
* Narrowed the output without changing the base pattern
Change one thing at a time.
Then generate again and confirm the result.
{% endstep %}
{% endstepper %}
## Common Issues and Solutions
"My table shows no rows"
Check these items:
* Confirm the template runs from `Account`
* Confirm the test account has related `Opportunity` records
* Verify the `WHERE` clause uses `AccountId = '{{!Account.Id}}'`
* Test with a record you know has child records
"My values are under the wrong headers"
Check these items:
* Compare the header order with the `` order
* Make sure each header has one matching query field
* Add fields one at a time when expanding the table
"One column is blank"
Check these items:
* Verify that field appears in the `SELECT` clause
* Verify the same field appears in the matching `` tag
* Confirm the returned records actually contain data in that field
"The wrong records are returned"
Check these items:
* Review the relationship field in the `WHERE` clause
* Confirm the base merge field points to the current record
* Remove extra filters and test the base query first
"How do I adapt this to another object pair?"
Use this swap pattern:
* Change the base template object
* Change the child object in `FROM`
* Change the relationship field in `WHERE`
* Change the selected fields, headers, and `` tags together
Keep the overall table structure the same.
## What You've Learned
✅ Built a related list table from an `Account` template\
✅ Queried `Opportunity` records with ``\
✅ Tied the query to the current base record\
✅ Matched headers to `` tags in the correct order\
✅ Reused one example pattern that can scale to other objects
## Next Steps
### Adapt the pattern
* Replace `Opportunity` with `Contact` on an `Account` template
* Change the visible columns for a different use case
* Add one more field and test it by itself
### Combine it with other features
* Use [Getting Started with Conditional Logic](/quick-start/template-building/conditional-logic-tutorial) to show the table only when related opportunities exist
* Use [Template Attributes Tutorial](/quick-start/template-building/how-to-format-text-dates-and-currency) to format dates, numbers, and output values inside the table
* Use [Creating Your First Named Query](/quick-start/template-building/creating-your-first-named-query-tutorial) when you need one reusable result outside a table
## Practice Exercise
Build an `Account` template that includes:
1. A header with `Account.Name` and `Account.Owner.Name`
2. A four-column related list table for opportunities
3. One query tied to the current account
4. A test run against an account with related opportunities
5. One filtered variation that only shows open opportunities
Bonus challenges:
* Rebuild the same pattern for `Account` and `Contact`
* Change the sort order
* Add one more displayed field
# Setup Calculations
Learn the basic math tag patterns for numbers, dates, conditions, and null-safe output.
## What You'll Learn
In this tutorial, you'll build a quote summary that uses calculation tags to produce clean numeric and date output. By the end, you'll know how to:
* Calculate a deposit amount with `