PMIS Report Generation Fixes

Current behavior

• Groups invoice PDF preparation by company and selected report before calling the standard implementation in that company's context.

• For account.report_invoice_with_payments batches containing multiple unique record IDs, prepares PDF streams separately for each existing invoice in its own company, preserving requested order.

• Uses the normal rendering path for single records, duplicate-ID batches, other reports, and calls already carrying the recursion guard.

• Renders unskipped dynamic reports in the invoice company and adds their PDFs to the mail attachment widget.

• Logs preparation, stream, dynamic-report, and attachment metadata. Mail parameters are otherwise returned unchanged.

Usage and limits

Use the normal invoice sending workflow and select the required report and attachments. No manual repair action or background job is introduced.

The addon does not unconditionally regenerate every stored PDF or invalidate all cached attachments; standard report behavior still applies. Missing records are skipped in the per-record batch path. Report-generation failures are not silently converted into successful sends.

Diagnostic logs include record identifiers, company/user information, report details, attachment sizes, and context. Restrict access to logs and redact them before sharing. Tests use controlled report responses; they do not establish visual PDF fidelity for every installed report template.

Bug Tracker

Bugs are tracked on PMISuite Repository Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Credits

Maintainers

Current maintainer:

Luxim is an independent R&D and deployment company focused on solving complex problems in the Odoo ecosystem.

Luxim is an active member of OCA (Odoo Community Association).