Best practices for admins
How to run DynoMerge for a team without becoming the help desk.
Template library management
- One name, one template. Saving or importing with an existing name
updates that entry in place — use it. "Quote v2 FINAL (3)" chaos can't
happen if you keep names stable.
- Export the library after every meaningful change (⬇ Export library).
The .json is your backup AND your distribution file.
- Descriptors travel with templates. Build child tables via the panel
(loop picker or Add table to setup) and save — the data setup is embedded;
reps never see or touch it.
- Keep a "golden" folder of exported .json files in version control or
shared drive, dated.
Rolling out to a team
- Build and test templates in your own panel against real records.
- Export the library .json.
- Send reps: the extension (Web Store link), the .json, and two
instructions — Import this file and switch to end-user mode (footer
link). End-user mode hides all authoring; reps see Load-and-generate
only.
- Updates = send a new .json; same-name imports replace cleanly.
Guardrails to communicate
- End-user mode is a UX simplification, not security — permissions are
enforced by Salesforce (field-level security applies to every merge).
- Generated documents belong wherever your data policy says; Attach to
record keeps them inside Salesforce and is the audit-friendly default.
- Report grabs capture what the user can already see — nothing more.
Template design workflow that scales
- Start every template from the field finder — copy real tags, never type
paths from memory.
- Keep one sample record per object with rich data (all fields filled,
3+ child records) as your test target.
- Test the empty cases too: a record with no line items, blank optional
fields. Add
{#field}…{/} guards where blanks would look broken.
- Date/currency formatting belongs in filters, not in the data.
Performance notes
- Merges are instant; the API calls are the only wait (~1s live).
- Batch zip of hundreds of records: fine, but do it from CSV (one export)
rather than hundreds of live calls.
- Very long reports: prefer CSV export over repeated grabs.
When something breaks
Common errors covers every known message. The fastest
diagnostic: does the panel's tag list (Template setup, after loading) match
what you expect? 90% of issues are tag/data mismatches visible right there.
