Understand the credit-note bulk-export defect | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-credit-note-bulk-export-defect Publisher: Pixie Technologies LLC Bulk export and operational limitations Understand the credit-note bulk-export defect Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Avoid relying on the offered credit-note bulk action in the supplied version. Audience: CRM staff; Permission: e-Invoice: Bulk Export; Module v1.0.0; Where to goAdmin Area → Utilities → Bulk Export → Export Type: Credit Note 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 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. Follow these steps - Do not use this path for production until corrected and tested. - Use individual credit-note e-Invoice View/Download as the supported alternative. - After a code fix, test model loading, query table, date column, numbering and template output. Fields and options 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 EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - 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. 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. Important code-backed limitationCredit-note bulk export is a verified implementation defect in version 1.0.0 and may fail or export incorrect records. Related guides e-Invoice module overview (https://pixiecrm.com/help-centre/e-invoice-module-overview)Bulk export invoice e-Invoices (https://pixiecrm.com/help-centre/bulk-export-invoice-e-invoices)Prepare the e-Invoice temporary folder (https://pixiecrm.com/help-centre/prepare-the-e-invoice-temporary-folder)Understand e-Invoice bulk ZIP structure (https://pixiecrm.com/help-centre/understand-e-invoice-bulk-zip-structure)Generate and export an e-invoice (https://pixiecrm.com/help-centre/generate-and-export-an-e-invoice)Send an invoice to a customer (https://pixiecrm.com/help-centre/send-an-invoice-to-a-customer)