Excel (XLSX)

Choose XLSX when you need spreadsheet-first output, Excel-native formatting, and bracket-based Microsoft template syntax.

Use this page when you want to design a workbook in Microsoft Excel and generate a true .xlsx file from Salesforce data.

An XLSX template is built in Excel, then uploaded to S-Docs for generation.

Use it when spreadsheet structure matters more than HTML layout, Word editing, or slide design.

Pick XLSX when you need spreadsheet-first output, Excel design tools, and bracket-based S-Docs syntax.

When XLSX is the right fit

Use XLSX templates when you need:

• Microsoft Excel workbook design tools
• a generated .xlsx file
• merge fields inside a workbook
• conditional sections in worksheet content
• named queries in Microsoft template syntax
• generation through S-Docs LWCs or the SDK with the newer upload flow

XLSX is a strong fit for data exports, pricing workbooks, operational reports, and spreadsheet-first deliverables.

How XLSX templates work

The workbook design lives in Excel.

The dynamic data comes from S-Docs syntax placed inside the .xlsx file.

XLSX templates use bracketed Microsoft template syntax around S-Docs blocks and merge fields.

xlsx-basic-syntax.txt

[{{!Account.Name}}]

[<!--RENDER='{{!Opportunity.StageName}}' == 'Closed Won' -->]
  Closed-won summary
[<!--ENDRENDER-->]

Conditional logic

Use conditional logic when worksheet content should appear only for certain records.

XLSX conditional logic uses the same RENDER model as other Microsoft templates.

Wrap both the opening and closing tags in square brackets.

xlsx-render-block.txt

[<!--RENDER='{{!Contact.Phone}}' != 'NULL' -->]
  Phone: [{{!Contact.Phone}}]
[<!--ENDRENDER-->]

Keep merge fields inside rendered content in square brackets too.

Use the same operators you use in standard S-Docs conditional logic.

xlsx-render-operators.txt

[<!--RENDER=( ('{{!Account.BillingState}}' == 'CA' || '{{!Account.BillingState}}' == 'NV')
             && '{{!Account.Active_Contract__c}}' == 'True' ) -->]
  Regional account with active contract
[<!--ENDRENDER-->]

Nested render blocks work too.

xlsx-render-nested.txt

[<!--RENDER='{{!Opportunity.StageName}}' == 'Closed Won' -->]
  Congratulations on your purchase.
  [<!--RENDER1='{{!Opportunity.Install_Date__c}}' != 'NULL' -->]
    Installation is scheduled for [{{!Opportunity.Install_Date__c}}].
  [<!--ENDRENDER1-->]
[<!--ENDRENDER-->]

Common fixes:

• If the block prints as text, add square brackets around both RENDER tags.
• If a field inside the block stays blank, wrap that merge field in square brackets too.
• If the condition never matches, verify the field path and comparison value.

Starting with S-Docs Summer '25 (v10.0), XLSX generation uses the newer Microsoft template upload flow when enabled.

That improves consistency, file handling, and performance for supported generation paths.

Supported features

XLSX templates support these common S-Docs capabilities:

• merge fields
• conditional logic
• named queries
• Excel-native formatting and formulas

Important constraints

Keep these XLSX rules in mind:

• Live Edit is not supported.
• Template headers and footers are not supported.
• Component templates are not supported.
• S-Sign is not supported.
• Related lists are not supported.
• Leading zeros and strict number formats may need explicit Excel formatting.

Next reads by goal

• Need the build steps? Read Build and Upload an XLSX Template.
• Need setup details? Read XLSX Rendering Considerations.
• Need merge field syntax? Read Merge Fields With Microsoft Templates (DOCX, PPTX, XLSX).
• Need conditional syntax? Read Quick Setup: Conditional Logic With Microsoft Templates (DOCX, PPTX, XLSX).
• Need named query patterns? Read How To: Advanced Data Retrieval with Named Queries.
• Need formatting help for leading zeros? Read Preserve leading zeros in Excel output.