[trunk, 7.0, 6.1] some data may not be updated because they are part of customization

Bug #1190444 reported by invitu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Won't Fix
Wishlist
OpenERP R&D Addons Team 3
OpenERP Community Backports (Addons)
Status tracked in 7.0
6.1
Opinion
Wishlist
invitu
7.0
Opinion
Wishlist
invitu

Bug Description

the data located in account/account_report.xml and sale/sale_report.xml should not be updated because these data are part of customization

I suggest not to update them

by the way, xml files listed in init_xml seem to be updated...
do we need to set the noupdate=1 in data section of xml file ?

Related branches

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: Undecided → Wishlist
status: New → Confirmed
invitu (invitu)
description: updated
invitu (invitu)
description: updated
Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

Hi Invitu,

I am not convinced of making such data noupdate. What exactly are the changes that you want to preserve in these reports?

Revision history for this message
Nhomar - Vauxoo (nhomar) wrote :

Hello Stefan.

Yes I am agreed wtih you, and I make the same question, the correct solution is noupdate only the data that should be customized.

Some times customize is better with a Functional Duplicate.

Regards.

Revision history for this message
invitu (invitu) wrote :

Dear all

In our case, the usage=default and the attachment (for invoices) properties should not be updated because we use a custom webkit report for sale orders and invoices.
In v6.1, the reports are sent by email via edi module that calls the default report for each object. When we update the addons, we have to manually remove the default property from original reports

Olivier Dony explained here (https://bugs.launchpad.net/openobject-addons/+bug/1190313/comments/8) that the edi module is not used anymore for sending emails in v7.0

What are your advices ?

Best Regards

invitu (invitu)
Changed in openobject-addons:
status: Confirmed → Opinion
Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

Thanks for the explanation. I think it actually makes sense but it should involve a clear decision from OpenERP SA on a policy around this and an exhaustive patch covering all reports (assuming that this should go for all reports in the system).

Revision history for this message
invitu (invitu) wrote :

On the other hand, is there a clear reason for updating reports ? In 100% cases we had, reports were always customized...

Revision history for this message
Martin Trigaux (OpenERP) (mat-openerp) wrote :

Hello guys,

As you said, there is no real reason to customise a report declaration. As mentioned Olivier in the bug lp:1190313 the filed usage is no longer used.
You could change the path to rml report but that means creating a new report...

So without valid reason we will not put noupdate on reports.

Regards

Changed in openobject-addons:
status: Opinion → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.