audrius/reporting-engine
1
0
Fork 1
mirror of https://github.com/OCA/reporting-engine.git synced 2025-02-16 16:30:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

[FIX] report_display_name_in_footer: Param with noupdate

Browse Source
This commit is contained in:
Eduardo De Miguel
2024-06-20 11:39:23 +02:00
parent 9247622278
commit ea0e4319b5
4 changed files with 79 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
report_display_name_in_footer/README.rst
View File

@@ -107,6 +107,29 @@ To use this module, you need to:
3. Print a report for you desired model.
4. Check Footer to see document name.
Known issues / Roadmap
======================
When this module is checking if the model has to display the name in the
footer is done at the level of the initial model of the report you are
printing.
Examples of strange cases/uses: *stock_picking_batch_print_pickings* and
*stock_picking_batch_print_invoices* modules print the delivery notes or
invoices of the Pickings associated with the Batch, but the report is
being launched from the Batch. So, the header and footer belongs to the
Batch.
Within that report, calls are made to the invoice or delivery note
reports, but the check to see if the name of the document has to be
printed in the footer is done on the Batch.
Therefore, if you set the configuration parameter to "stock.picking,
account.move" , the names printed from that report will not appear. By
setting it to "stock.picking.batch", the module will establish that all
the documents contained in that report (whether invoices or delivery
notes) must include the name in the footer.
Bug Tracker
===========

2
report_display_name_in_footer/data/report_data.xml
View File

@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8" ?>
<odoo noupdate="0">
<odoo noupdate="1">
<record id="display_name_in_footer_models_param" model="ir.config_parameter">
<field name="key">report.display_name_in_footer_models</field>
<field name="value">all</field>

18
report_display_name_in_footer/readme/ROADMAP.md Normal file
View File

@@ -0,0 +1,18 @@
When this module is checking if the model has to display the name in the footer
is done at the level of the initial model of the report you are printing.
Examples of strange cases/uses:
*stock_picking_batch_print_pickings* and *stock_picking_batch_print_invoices* modules
print the delivery notes or invoices of the Pickings associated with the Batch,
but the report is being launched from the Batch. So, the header and footer
belongs to the Batch.
Within that report, calls are made to the invoice or delivery note reports,
but the check to see if the name of the document has to be printed in the
footer is done on the Batch.
Therefore, if you set the configuration parameter to "stock.picking, account.move"
, the names printed from that report will not appear.
By setting it to "stock.picking.batch", the module will establish that all the
documents contained in that report (whether invoices or delivery notes)
must include the name in the footer.

51
report_display_name_in_footer/static/description/index.html
View File

@@ -8,10 +8,11 @@
/*
:Author: David Goodger (goodger@python.org)
:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $
:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
Despite the name, some widely supported CSS2 features are used.
See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to
customize this style sheet.
@@ -274,7 +275,7 @@ pre.literal-block, pre.doctest-block, pre.math, pre.code {
margin-left: 2em ;
margin-right: 2em }
pre.code .ln { color: grey; } /* line numbers */
pre.code .ln { color: gray; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
@@ -300,7 +301,7 @@ span.option {
span.pre {
white-space: pre }
span.problematic {
span.problematic, pre.problematic {
color: red }
span.section-subtitle {
@@ -387,11 +388,12 @@ Only for development or testing purpose, do not use in production.
<li><a class="reference internal" href="#use-cases-context" id="toc-entry-1">Use Cases / Context</a></li>
<li><a class="reference internal" href="#configuration" id="toc-entry-2">Configuration</a></li>
<li><a class="reference internal" href="#usage" id="toc-entry-3">Usage</a></li>
<li><a class="reference internal" href="#bug-tracker" id="toc-entry-4">Bug Tracker</a></li>
<li><a class="reference internal" href="#credits" id="toc-entry-5">Credits</a><ul>
<li><a class="reference internal" href="#authors" id="toc-entry-6">Authors</a></li>
<li><a class="reference internal" href="#contributors" id="toc-entry-7">Contributors</a></li>
<li><a class="reference internal" href="#maintainers" id="toc-entry-8">Maintainers</a></li>
<li><a class="reference internal" href="#known-issues-roadmap" id="toc-entry-4">Known issues / Roadmap</a></li>
<li><a class="reference internal" href="#bug-tracker" id="toc-entry-5">Bug Tracker</a></li>
<li><a class="reference internal" href="#credits" id="toc-entry-6">Credits</a><ul>
<li><a class="reference internal" href="#authors" id="toc-entry-7">Authors</a></li>
<li><a class="reference internal" href="#contributors" id="toc-entry-8">Contributors</a></li>
<li><a class="reference internal" href="#maintainers" id="toc-entry-9">Maintainers</a></li>
</ul>
</li>
</ul>
@@ -452,8 +454,27 @@ type of documents.</li>
<li>Check Footer to see document name.</li>
</ol>
</div>
<div class="section" id="known-issues-roadmap">
<h1><a class="toc-backref" href="#toc-entry-4">Known issues / Roadmap</a></h1>
<p>When this module is checking if the model has to display the name in the
footer is done at the level of the initial model of the report you are
printing.</p>
<p>Examples of strange cases/uses: <em>stock_picking_batch_print_pickings</em> and
<em>stock_picking_batch_print_invoices</em> modules print the delivery notes or
invoices of the Pickings associated with the Batch, but the report is
being launched from the Batch. So, the header and footer belongs to the
Batch.</p>
<p>Within that report, calls are made to the invoice or delivery note
reports, but the check to see if the name of the document has to be
printed in the footer is done on the Batch.</p>
<p>Therefore, if you set the configuration parameter to “stock.picking,
account.move” , the names printed from that report will not appear. By
setting it to “stock.picking.batch”, the module will establish that all
the documents contained in that report (whether invoices or delivery
notes) must include the name in the footer.</p>
</div>
<div class="section" id="bug-tracker">
<h1><a class="toc-backref" href="#toc-entry-4">Bug Tracker</a></h1>
<h1><a class="toc-backref" href="#toc-entry-5">Bug Tracker</a></h1>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/reporting-engine/issues">GitHub Issues</a>.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
@@ -461,24 +482,26 @@ If you spotted it first, help us to smash it by providing a detailed and welcome
<p>Do not contact contributors directly about support or help with technical issues.</p>
</div>
<div class="section" id="credits">
<h1><a class="toc-backref" href="#toc-entry-5">Credits</a></h1>
<h1><a class="toc-backref" href="#toc-entry-6">Credits</a></h1>
<div class="section" id="authors">
<h2><a class="toc-backref" href="#toc-entry-6">Authors</a></h2>
<h2><a class="toc-backref" href="#toc-entry-7">Authors</a></h2>
<ul class="simple">
<li>Moduon</li>
</ul>
</div>
<div class="section" id="contributors">
<h2><a class="toc-backref" href="#toc-entry-7">Contributors</a></h2>
<h2><a class="toc-backref" href="#toc-entry-8">Contributors</a></h2>
<ul class="simple">
<li>Eduardo de Miguel (<a class="reference external" href="https://www.moduon.team/">Moduon</a>)</li>
<li>Rafael Blasco (<a class="reference external" href="https://www.moduon.team/">Moduon</a>)</li>
</ul>
</div>
<div class="section" id="maintainers">
<h2><a class="toc-backref" href="#toc-entry-8">Maintainers</a></h2>
<h2><a class="toc-backref" href="#toc-entry-9">Maintainers</a></h2>
<p>This module is maintained by the OCA.</p>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<a class="reference external image-reference" href="https://odoo-community.org">
<img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" />
</a>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>