When l10n_latam_invoice_document is installed and the current company does not have a custom header (in stable, only Chile and Argentina with their localization installed use custom header), printing multiple invoice at once, one out of two had no header or footer. This is because `<div class="header"/>` and `<div class="footer"/>` should be unique per record being printed, and when a custom header was not used they were duplicated with the duplicate empty. As an example, if we had 3 documents: - record 1 : good header - record 1 : empty header - record 1 : body - record 1 : good footer - record 1 : empty footer - record 2 : good header - record 2 : empty header - record 2 : body - record 2 : good footer - record 2 : empty footer - record 3 : good header - record 3 : empty header - record 3 : body - record 3 : good footer - record 3 : empty footer When we give them to wkhtmltopdf, it would be mismatched: - headers: - record 1 : good header - record 1 : empty header - record 2 : good header - bodies: - record 1 : body - record 2 : body - record 3 : body - footers: - record 1 : good footer - record 1 : empty footer - record 2 : good footer so record 2 will have empty header/footer, and record 3 will get those of record 2. opw-2507137 closes odoo/odoo#69703 X-original-commit: 90bdb5c7b7aa6a9b98e9acb1774d449ae65a3918 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
The name of your first customer invoice is a configuration that determines the next ones. The problem before is that when you confirmed a first invoice, you could not alter its document number anymore. With this commit, as long as it is the first invoice, you can still change the document number when you reset to draft.
This new field was introduced in master by https://github.com/odoo/odoo/commit/013936261b26c601ce55015dbbbb99a7313a9a39 , making l10n_latam_country_code redundant. closes odoo/odoo#56181 Related: odoo/upgrade#1666 Signed-off-by: Laurent Smet <smetl@users.noreply.github.com>
port foward from 13.0 branch, also remove the logic of _get_name_invoice_report() method already added in account module and remove the not needed latam report templates.
The latam docuemnts used for document type an document number are not showed correctly in the view, they displaying to close side by side and the related labels are not show. After this PR this has been fixed and now we have the labels and the proper separation of the fields in the invoice form view. closes odoo/odoo#55648 Signed-off-by: Josse Colpaert <jco@openerp.com>
When printing an invoice using l10n_latam_invoice_document it crashes as res.partner does not have an attribute 'l10n_latam_identification_type_id', keeping the whole xpath is not needed as the VAT label is already considered in the account module: https://github.com/odoo/odoo/blob/13.0/addons/account/views/report_invoice.xml#L10 closes odoo/odoo#48800 X-original-commit: 9f0bf9bcaa6c21c36d5abdc5316aa80cef67f12f Signed-off-by: Josse Colpaert <jco@openerp.com>
* remove logic of sequences in invoices and use new logic to set invoices sequences. * re add l10n_latam_document_number field to make the sequence set possible. * replace type field with move_type field in model account.move * add new field l10n_latam_manual_number to know when the document number should be or not set * update compute highest_name everytime that the journal and document type change. * implement how we deal with first number * for customer invoices only compute the name after they has been posted * be able to search by document type code * update translations
l10n_latam_country_code field is no more needed for account.move object thanks to commit 7edb5c11 Also, since country_code field has been defined in view_move_form, no need to redefine it when it is inherited in l10n_cn module. closes odoo/odoo#48719 Task: 2228210 Signed-off-by: Josse Colpaert <jco@openerp.com>
Task 2146469 Rework the name computation: * It doesn't use ir.sequence anymore * It is an editable computed field * Add a renaming tool This allows the user to tweak the sequences more easily than having to get through the ir.sequence settings. The sequence depends on a parameter of the journal: continuous, montly and yearly restart of the sequence. Everytime a new period is started, try to make a pattern form another period. The incrementing is done by taking the previous name, ordered lexicographically, splitting it by taking the digits at the end, adding 1 and re contstruct with the prefix. ** This means there could be cases where the prefix has a big importance on the next number. For instance, if you have INVOICE/2019/0001 INVOICE/2019/0002 and then rename the last one to INV/2019/0002, don't expect the next number to be INV/2019/0003. It will be INVOICE/2019/0002 (again) because the highest number was INVOICE/2019/0001. You will then end up with INVOICE/2019/0001 INV/2019/0002 INVOICE/2019/0002 closes odoo/odoo#41485 Related: odoo/enterprise#7189 Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
pass move type to journal for filtration but it is removed by this commit https://github.com/odoo/odoo/commit/a9b762870651e607b244d8fd5681a9f3557cc0e9#diff-59b30a3c3997659843dcc916225f508a so no more in use closes odoo/odoo#44636 X-original-commit: 06bcfa8f946485ca2979511144bc5f22a3ca118c Signed-off-by: Josse Colpaert <jco@openerp.com>