Archives
Contributors
Re: Paperformat issues (Odoo14)
Hi Tom,
Thanks for the super quick response.
AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated
That actually make sense for me, so since I was testing a custom report I've tried to reproduced the situation on OCA/reporting-engine odoo14 instance, unfortunately I must confirm what I've said in previous message: if you leave paper format margin bottom value to 0px the footer will not be rendered with or without the installation of module report_qweb_element_page_visibility .
I've taken notes of all steps to reproduce this behaviour, you can read detailed steps below. Is there anything we can do? Should I open an issue for the module?
I don't think it's strictly related, so I'm not sure what to do here.
Steps to reproduce (example with sale order report)
ADD VISIBILITY CLASS (render footer only in last page)
- go on Settings > search for > search for "Document Layout", ensure the "external_layout_standard" or another layout is set
- open the document layout by "external-link" window, find the "div" with footer class and add class "last-page"
ENSURE PAPER FORMAT USAGE ON REPORT
- go on Technical > Actions > Reports , select the one named "Quotation / Order"
- set "A4" record as value for "Paperperformat" field, then click to open the paperformat (or go on Technical > Reporting > Paper Format, and select the A4 paperformat)
CHANGE PAPER FORMAT PARAMETER
- set margin bottom to 0px
PREPARE SALE ORDER DOCUMENT
- make a sale order that will have enough products to generate a report of at least 2 pages (around 25 products should be fine for the standard report)
PRINT DOCUMENT
- on the sale order click "Print" > Quotation / Order
CURRENT BEHAVIOUR
Footer will not be rendered on last page (I posted the report in attachments)
It sounds a bit paradoxical that you define a bottom margin for the report which is then occupied :)
AFAIK the report_qweb_element_page_visibility operates on the area outside the margins of the "content area" so the two things should be clearly separated
Do you perhaps have a screenshot with some arrows and circles highlighting what you mean
On 6/7/24 12:13, Francesco Ballerini wrote:
Hi,
I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.
I need to define a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page
So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.
Did you ever come up with a solution to this ? Any kind of workaround is fine :)
Thank you--Francesco Ballerini
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 02:46 - 7 Jun 2024
Reference
-
Paperformat issues (Odoo14)
Hi,
I am using this module report_qweb_element_page_visibility to be able to show footer conditionally in reports, but I'm having issues with paperformat.
I need to define a "margin botton" paperformat parameter in order to let the footer get the proper space when it needs to be rendered, although by defining a static paperformat margin bottom the space of the footer will always be occupied in the report, even if the footer is not displayed by the class last-page/first-page
So the OCA module works properly, but I think that the margin bottom paperformat parameter is not flexible enough to support this situation.Did you ever come up with a solution to this ? Any kind of workaround is fine :)Thank you--Francesco Ballerini
by Francesco Ballerini - 12:11 - 7 Jun 2024