Bulk export and operational limitations

Understand the credit-note bulk-export defect

Avoid relying on the offered credit-note bulk action in the supplied version.

Audience: CRM staffPermission: e-Invoice: Bulk ExportModule v1.0.0
Exact navigationAdmin Area → Utilities → Bulk Export → Export Type: Credit Note
Before you begin
  • 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 covers

Avoid relying on the offered credit-note bulk action in the supplied version. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Do not use this path for production until corrected and tested.
  2. Use individual credit-note e-Invoice View/Download as the supported alternative.
  3. After a code fix, test model loading, query table, date column, numbering and template output.

Fields, choices and supported possibilities

Action scopeAvoid relying on the offered credit-note bulk action in the supplied version.
Module version1.0.0
NavigationAdmin Area → Utilities → Bulk Export → Export Type: Credit Note
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • BulkExporter always selects from the invoices table.
  • Its processing path calls invoices_model->get even when credit_note was selected, while only credit_notes_model may have been loaded.

Expected result and verification

  • 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.
Important code-backed limitationCredit-note bulk export is a verified implementation defect in version 1.0.0 and may fail or export incorrect records.