Symptom → cause → fix, for every message you're likely to meet.
Cause: the template asks for a field that object doesn't have. Two
classic versions: an Account template run on an Opportunity page, or a
hand-built child table using a field name that doesn't exist on the child
object (some objects, like OpportunityHistory, have no Name field).
Fix: open the record type the template was built for — DynoMerge tells you which ("This template is built for X records"). For child tables, build them with the loop-table picker or ➕ Add table to setup — both verify every field against the org before writing tags.
Cause 1 — smart quotes: a filter argument's quotes got curled by Word/Google Docs, breaking the tag's parse. Fix: retype with straight quotes (and disable smart quotes — see Word templates).
Cause 2 — path mismatch: the tag doesn't match the data (e.g. tag says
{Opportunity.Name} but your CSV has no descriptor mapping, so the real key
is the column header). Fix: use the tags shown in the panel's field finder /
report columns list — they're always correct for the loaded data.
Cause: the tags are present but the DATA setup doesn't include the child table — tags say what to print, the data setup says what to fetch.
Fix: Edit template tab → Browse fields → click the child relationship (e.g. OpportunityLineItems) → check the fields → ➕ Add table to setup → Save the template. Or insert via the ⊞ loop table picker, which wires both at once.
Cause: Salesforce only renders the rows on screen for long reports.
Fix: scroll the report to reveal more rows, then click Grab more rows — each grab adds the newly visible rows until the status says "All ~N records captured." For very long reports, CSV export is one click and always complete.
Cause: your Salesforce login session ended (logout, timeout, password change).
Fix: refresh the Salesforce tab, log in if prompted, and reconnect in the panel. DynoMerge never stores your password — it rides your existing login.
Cause: template written for one object alias (say Opportunity.), but
you're merging a different object or a CSV whose alias box says something
else.
Fix: set Record name / alias in template on the Generate tab to match the prefix your tags use — or open the matching record type.
Cause: usually field-level security — the API only returns fields YOUR user can see. A field hidden from your profile merges as blank.
Fix: check the field in Salesforce itself; if you can't see it there, ask your admin. (This is a feature: DynoMerge can never leak data your login can't access.)
Cause: browsers can't attach files to web links — a platform rule, not a bug. The .docx downloads instead.
Fix: drag the file from Chrome's download bar into the message, or use the system share sheet button when offered (it attaches automatically). On the mobile app, sharing always attaches natively.
Cause: removing the extension deletes its storage.
Fix for next time: ⬇ Export library before updating, Import it after. (Updates installed from the Chrome Web Store keep storage — this only affects remove-and-reinstall of unpacked versions.)