# Additional Resources

Use this section when you need a focused solution that does not fit a broader workflow page.

These articles cover uncommon formatting patterns, merge field fixes, and Salesforce-specific template behavior.

Use the links below to jump straight to the issue you need.

{% hint style="info" %}
Use the main workflow sections first when you need end-to-end setup.

Use this section when you already know the specific issue you need to solve.
{% endhint %}

### Start with the path that fits your goal

If a merge field breaks because of punctuation, start with apostrophe handling.

If you need better address output or deeper relationship traversal, use the Salesforce-focused guides.

If rich text adds extra spacing, start with the formatting article.

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Escape an Apostrophe Correctly in a Merge Field</strong></td><td>Prevent merge field failures when field values include apostrophes.</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/6bf519bef231ce5d7d8edc8cd875b27750faa0d7">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/6bf519bef231ce5d7d8edc8cd875b27750faa0d7</a></td></tr><tr><td><strong>Mailing Address Fields</strong></td><td>Format Salesforce address data with individual field components instead of compound address fields.</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/153f0d1510d9d9ae743210b1f48b7cec63172f96">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/153f0d1510d9d9ae743210b1f48b7cec63172f96</a></td></tr><tr><td><strong>Quickly Traverse Five Levels</strong></td><td>Reference deeper Salesforce relationships in merge fields and SOQL.</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/9da41e6af4862cad6519d96d7524d8ca408aa41a">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/9da41e6af4862cad6519d96d7524d8ca408aa41a</a></td></tr><tr><td><strong>Rich Text Field Formatting Considerations</strong></td><td>Remove extra spacing and control paragraph tags in rich text output.</td><td><a href="/spaces/WKNnJmhJBQwhdk5WBFsi/pages/c3f72209567e5aa2c7bf69d0696c923115a0a85f">/spaces/WKNnJmhJBQwhdk5WBFsi/pages/c3f72209567e5aa2c7bf69d0696c923115a0a85f</a></td></tr></tbody></table>

### What you can do with additional resources

* Fix merge fields that fail on apostrophes.
* Format mailing addresses with full control over layout.
* Traverse up to five relationship levels in queries and merge fields.
* Clean up rich text spacing in merge fields and related lists.

### Browse by topic

* [Escape an Apostrophe Correctly in a Merge Field](/sdocs/template-architecture/inserting-merge-fields/additional-resources/escape-an-apostrophe-correctly-in-a-merge-field.md)
* [Mailing Address Fields](/sdocs/template-architecture/inserting-merge-fields/additional-resources/special-salesforce-mailing-address-fields.md)
* [Quickly Traverse Five Levels](/sdocs/template-architecture/inserting-merge-fields/additional-resources/quickly-traverse-five-levels.md)
* [Rich Text Field Formatting Considerations](/sdocs/template-architecture/inserting-merge-fields/additional-resources/concerns-with-using-rich-text-field-formatting.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/sdocs/template-architecture/inserting-merge-fields/additional-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
