Understand Delivery Note invoice-payload isolation

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

Explain how module fields are prevented from entering the core invoice insert or update payload.

What this guide helps you do

Explain how module fields are prevented from entering the core invoice insert or update payload. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

1. Submit an invoice with or without Add Delivery Note.
2. Verify the core invoice saves normally.
3. Inspect the module’s before-invoice add/update filter.
4. Check delivery-note keys are captured for the module and removed from the invoice data array.
5. Check the after-invoice hook creates or updates only module-owned records.

Fields and options

• Checkbox flag and delivery fields are module-only payload keys
• Temporary captured payload is associated with the invoice save request
• Core invoice columns remain unaffected

Rules and limits

• The isolation filter runs for invoice add and update.
• The module is designed to be portable and makes no invoice-table schema change.
• An invoice update does not create another note when a non-void note already exists.

Check it worked

• Core invoicing remains compatible while the optional module workflow receives its own values.

Safety checks and troubleshooting

• Do not add Delivery Note columns to the core invoice table to reproduce this behaviour.

Related guides