Check and save

Check your tags

Open the Check tab and press Check. Every tag in the document, headers and footers included, is checked against your org:

• A tag that matches no field is marked Unresolved, with the reason (“Not a field of Account.”).
• Fields used in the wrong list scope are flagged.
• Tags left behind by another document tool are listed under Not recognised.

Click any row to jump to that tag in the document. The Highlight tags toggle shades every tag while you work; the shading is removed automatically when you save.

Opening the tab does not run the check, because reading the whole document takes a moment. The count on the tab tells you whether a check has run and what it found. The full check in Salesforce still runs when you save.

The pane never guesses a correction (“did you mean…?”). A near-miss guess on somebody else’s tag is confidently wrong often enough that a bad suggestion costs more than none.

Save to Salesforce

1. Open the Save tab.
2. The card at the top says where this save is going: a new template, or a new version of one you have saved before, with that template’s current status.
3. Give the template a name. It defaults to the document’s file name. Saving a new version of an existing template shows the stored name instead, so a save can never rename it by accident.
4. The base object is shown read-only; change it on the Build tab.
5. Click Save template (or Save new version) in the bar at the bottom.

If the check found problems, a red banner on the Save tab says so and warns that the saved version will be marked Invalid until they are fixed. You can still save; the add-in never blocks you.

Save a new version of an existing template

Click ▤ My templates in the header to see the templates already saved for this base object. Pick one, and the next save creates a new version of it instead of a separate template. The Save tab’s card names the template you are versioning, and New template… in the Save to dropdown switches back. After any save, further saves from the same pane keep versioning that template.

You can revise a template at any time: open the document in Word, make your changes, and save again. Before the template is first published, a save updates the current draft in place; after that, each save creates a new version to proof and publish. See Word-file templates.

Read the save results

Saving uploads the document and checks every tag against your org. The Save results panel then appears under the Save tab, starting with a VALID or INVALID chip for the version just saved:

• A green banner means the template is valid and ready to publish.
• A red banner means some tags could not be matched. Fix them and save again.

Below the banner, every tag is listed with its status:

Status	Meaning
Resolved	Matches a real field.
Structural	A loop or condition tag. These are expected.
Unresolved	No matching field. This needs fixing.
FLS warning	The field exists, but the user generating the document may not be able to see it.

The panel also tells you, before you publish, whether the document can be produced as a PDF; see Generate and publish.

The bottom bar then offers:

• Generate: merge this saved version against a test record straight away.
• Open in Salesforce: opens the template in the Template Editor, on the version you just saved.
• Fix in Check: the tag list with jump-to-tag. It appears only when there is something to fix.

Fix unresolved tags

Unresolved tags almost always come from a typo, or a field that does not exist on the chosen object:

• Check the spelling against the field list on the Build tab.
• Re-insert the field from the picker instead of typing it by hand. That guarantees a valid tag.
• Make sure you picked the right base object on the Build tab. A field that is valid on Opportunity does not resolve on a template built for Account.

Fix the document in Word, then save again. Nothing you set on the Save tab (the target template, the base object, the test record) is lost by moving between tabs.