Single-document output and email

Handle no default e-Invoice template

Resolve the warning and redirect when a source document has no configured default. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Settings → Finance → e-Invoice
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 you’ll accomplish

Resolve the warning and redirect when a source document has no configured default. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Create a valid template.
  2. Select it as the relevant invoice or credit-note default.
  3. Save settings.
  4. Return to the source document and try View/Download again.

Fields and options to review

Action scopeResolve the warning and redirect when a source document has no configured default.
Module version1.0.0
NavigationAdmin Area → Setup → Settings → Finance → e-Invoice
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The output controller redirects to the relevant sales list/hash when the default template cannot be found.

How to confirm 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.