Customer work, connected.

Help & supportMyAccount
Template editor and validation

Troubleshoot invalid Mustache template syntax

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Resolve rendering exceptions before XML/JSON validation.

Audience: CRM staffPermission: AdministratorModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Settings → Finance → e-Invoice → Template → Validate
Before you start
  • Use an authorised account and confirm the source CRM record or setting is correct.
  • Follow the exact route shown above; do not force database values to imitate a completed action.

What this guide helps you do

Resolve rendering exceptions before XML/JSON validation. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Read the Invalid Mustache error.
  2. Check opening/closing variables and sections.
  3. Correct the template.
  4. Validate again.

Fields and options

Action scopeResolve rendering exceptions before XML/JSON validation.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice → Template → Validate
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules and limits

  • The server uses Mustache Engine with UTF-8, strict callables and a TEMP_FOLDER/mustache cache.

Check it worked

  • The requested record, output or setting is created or updated through the supported module flow.
  • Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
  • An error message is investigated rather than bypassed.

Security, privacy and operational checks

  • Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
  • Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
  • Test configuration changes with controlled records before production-wide use.
  • Retain or delete evidence only under an authorised retention process.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page