Overslaan naar inhoud
Odoo Menu
  • Aanmelden
  • Probeer het gratis
  • Apps
    Financiën
    • Boekhouding
    • Facturatie
    • Onkosten
    • Spreadsheet (BI)
    • Documenten
    • Ondertekenen
    Verkoop
    • CRM
    • Verkoop
    • Kassasysteem winkel
    • Kassasysteem Restaurant
    • Abonnementen
    • Verhuur
    Websites
    • Websitebouwer
    • E-commerce
    • Blog
    • Forum
    • Live Chat
    • eLearning
    Bevoorradingsketen
    • Voorraad
    • Productie
    • PLM
    • Inkoop
    • Onderhoud
    • Kwaliteit
    Personeelsbeheer
    • Werknemers
    • Werving & Selectie
    • Verlof
    • Evaluaties
    • Aanbevelingen
    • Wagenpark
    Marketing
    • Social media Marketing
    • E-mailmarketing
    • SMS Marketing
    • Evenementen
    • Marketingautomatisering
    • Enquêtes
    Diensten
    • Project
    • Urenstaten
    • Buitendienst
    • Helpdesk
    • Planning
    • Afspraken
    Productiviteit
    • Chat
    • Goedkeuringen
    • IoT
    • VoIP
    • Kennis
    • WhatsApp
    Apps van derden Odoo Studio Odoo Cloud Platform
  • Bedrijfstakken
    Detailhandel
    • Boekhandel
    • kledingwinkel
    • Meubelzaak
    • Supermarkt
    • Bouwmarkt
    • Speelgoedwinkel
    Food & Hospitality
    • Bar en Pub
    • Restaurant
    • Fastfood
    • Gastenverblijf
    • Drankenhandelaar
    • Hotel
    Vastgoed
    • Makelaarskantoor
    • Architectenbureau
    • Bouw
    • Vastgoedbeheer
    • Tuinieren
    • Vereniging van eigenaren
    Consulting
    • Accountantskantoor
    • Odoo Partner
    • Marketingbureau
    • Advocatenkantoor
    • Talentenwerving
    • Audit & Certificering
    Productie
    • Textiel
    • Metaal
    • Meubels
    • Eten
    • Brewery
    • Relatiegeschenken
    Gezondheid & Fitness
    • Sportclub
    • Opticien
    • Fitnesscentrum
    • Wellness-medewerkers
    • Apotheek
    • Kapper
    Trades
    • Klusjesman
    • IT-hardware & support
    • Zonne-energiesystemen
    • Schoenmaker
    • Schoonmaakdiensten
    • HVAC-diensten
    Andere
    • Non-profitorganisatie
    • Milieuagentschap
    • Verhuur van Billboards
    • Fotograaf
    • Fietsleasing
    • Softwareverkoper
    Browse all Industries
  • Community
    Leren
    • Tutorials
    • Documentatie
    • Certificeringen
    • Training
    • Blog
    • Podcast
    Versterk het onderwijs
    • Onderwijs- programma
    • Scale Up! Business Game
    • Bezoek Odoo
    Download de Software
    • Downloaden
    • Vergelijk edities
    • Releases
    Werk samen
    • Github
    • Forum
    • Evenementen
    • Vertalingen
    • Word een Partner
    • Services for Partners
    • Registreer je accountantskantoor
    Diensten
    • Vind een partner
    • Vind een boekhouder
    • Een adviseur ontmoeten
    • Implementatiediensten
    • Klantreferenties
    • Ondersteuning
    • Upgrades
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    Vraag een demo aan
  • Prijzen
  • Help

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • CRM
  • e-Commerce
  • Boekhouding
  • Voorraad
  • PoS
  • Project
  • MRP
All apps
Je moet geregistreerd zijn om te kunnen communiceren met de community.
Alle posts Personen Badges
Labels (Bekijk alle)
odoo accounting v14 pos v15
Over dit forum
Je moet geregistreerd zijn om te kunnen communiceren met de community.
Alle posts Personen Badges
Labels (Bekijk alle)
odoo accounting v14 pos v15
Over dit forum
Help

Odoo V8 problem: Custom Module inheriting account.invoice still loads standard invoice template - what am I doing wrong?

Inschrijven

Ontvang een bericht wanneer er activiteit is op deze post

Deze vraag is gerapporteerd
v8modulesinheritancereportingaccount.invoice
3 Antwoorden
7951 Weergaven
Avatar
NSC

My issue, see above... I created a custom module while studying some information about that in the web. But yet without any real success... I can install my module without any error messages and the appropriate menu entry appears in account.invoice view, but when pressing it, the old standard template is shown and not my own report template which is inside my external module. Can you tell me why not? I think, I did not do anything other than in former times for OpenERP v7, only considering API and report engine changes of Odoo v8.

What I have not yet understood, is how new report engine has to find my .xml report template (which replaces old .rml one). One of the blog entries I read about that claims, this template needs to be in folder "views" inside my module folder (not any more in folder "reports" like before with RML reporting) and that it is found there via its template_id. I did so - I put it there, but obviously, it is NOT found this way. But no example in the web regarding that issue uses an entire path to this report template like before with rml! Can anybody explain me how I have to "explain" the module where my own report template is located?

I used these tutorials as a base (sorry, I did not manage to insert them as links - this did not work; dunno why not):

http://www.zbeanztech.com/blog/qweb-report

http://blog.emiprotechnologies.com/create-qweb-report-odoo/


Here are some code sequences (please tell me where they are erroneous or incompatible with Odoo V8):

Report Parser and simple minimal report template to get started:

# -*- coding: utf-8 -*-
##############################################################################
# Modification of standard invoice template
##############################################################################

import time
from openerp.report import report_sxw
from openerp.osv import osv

class my_account_invoice(report_sxw.rml_parse):
def __init__(self, cr, uid, name, context):
super(fq_account_invoice, self).__init__(cr, uid, name, context=context)
self.localcontext.update({
'time': time,
})

#remove previous sale.report service :
#from netsvc import Service
#del Service._services['account.report_invoice']

class myreportinvoice(osv.AbstractModel): #individual name, but extending osv.AbstractModel
_name = 'report.account.report_invoice' #_name = ‘report.<module_name>.<report_name>’
_inherit = 'report.abstract_report'
_template='account.report_invoice' #_template = ‘<module_name>.<report_name>’
_wrapped_report_class=my_account_invoice #_wrapped_report_class = <parser_class_name>

<template id="report_invoice">
<t t-call="report.html_container">
<t t-foreach="docs" t-as="o">
<t t-call="report.external_layout">
<div class="page">
<h2>New Invoice Template</h2>
<p>This object's name is <span t-field="o.name"/></p>
</div>
</t>
</t>
</t>
</template>

Menu Entry:

<?xml version="1.0" encoding="utf-8"?>
<openerp>
<data>
<report
id="my_account_invoices"
model="account.invoice"
string="My New Invoice"
report_type="qweb-pdf"
name="account.report_invoice"
file="account.report_invoice"
attachment="(object.state in ('open','paid')) and ('INV'+(object.number or '').replace('/','')+'.pdf')"
attachment_use="False"
/>
</data>
</openerp>

If I replace the original ID 'report_invoice' to an own, individual one, for example 'report_my_invoice', I get the following error:
QWebTemplateNotFound: External ID not found in the system: account.report_my_invoice

But in settings --> reports, it looks like my new report is registered in a right way: The old original one has its own views, and my new one, too. Looks good, so far, but nevertheless, I can not print it because of this error. If it is registered with this ID in settings --> reports, why this error? Any idea ???



2
Avatar
Annuleer
Avatar
David Bertha
Beste antwoord

The module name should be your module name, not the name of the inherited module.

What's in your __openerp__.py file ?

I made a custom report for invoice too :

report_group_invoice.xml :

<?xml version="1.0" encoding="utf-8"?>
<openerp>
<data>
<template id="report_group_invoice_document">
...
</template>
<template id="report_group_invoice">
<t t-call="report.html_container">
<t t-foreach="doc_ids" t-as="doc_id">
<t t-raw="translate_doc(doc_id, doc_model, 'partner_id.lang', 'delivery_carrier_pickingup.report_group_invoice_document')"/>
</t>
</t>
</template>
</data>
</openerp>


report.xml :


<report 
id="delivery_grouped_invoice"
model="account.invoice"
string="Grouped invoice"
report_type="qweb-pdf"
name="delivery_carrier_pickingup.report_group_invoice"
file="delivery_carrier_pickingup.report_group_invoice"
attachment_use="True"
attachment="(object.state in ('open','paid')) and ('INV'+(object.number or '').replace('/','')+'.pdf')"
/>

Those 2 files are in the "data" list of my openerp.py file

If you want to add arguments to the qweb engine :


class GroupedInvoiceReport(models.AbstractModel):
_name = 'report.delivery_carrier_pickingup.report_group_invoice'
def render_html(self, cr, uid, ids, data=None, context=None):
"""Add period start and period end from context to args of report template"""
if context is None :
    context= {}
report_obj = self.pool['report']
report = report_obj._get_report_from_name(cr, uid, 'delivery_carrier_pickingup.report_group_invoice')
docargs = {
'doc_ids': ids,
'doc_model': report.model,
'docs': self.pool.get('account.invoice').browse(cr,uid, ids,context=context),
}
docargs.update(<arguments>)
return report_obj.render(cr, uid, ids, 'delivery_carrier_pickingup.report_group_invoice', docargs, context=context)

My answer to NSC :
A report entry (with the <report/> tag) define a report, not a menu entry : https://www.odoo.com/documentation/8.0/reference/reports.html


1
Avatar
Annuleer
NSC
Auteur

Okay then, maybe pointing out this misunderstanding of mine has already cleared up my mind for that - if report-tag is not only for menu entry but all the report definition, then model-tag inside seems to be underlying data source for it...

Avatar
NSC
Auteur Beste antwoord

This is an answer of @David Bertha's post - I can do what I want; it will not appear under the post it refers to :(:

Thank you for this, David! I think, you have just acknowledged what I found out later in the night! When refering to my own module overall and not any more to account, I was able to load my minimal template to get started when pressing the menu item! The only location left where I referenced account model is model field in menu entry (report.xml in your example). But this is only for the menu to know where to appear, isn't it?

What I am still wondering about is, how the module can know which data models it can access... I have not yet accessed any field for account.invoice in my getting-started-minimal-template (it is still nothing else than a skeleton), but I will try later on, if I can access any field.

In every case, if the "original" id/model should not be referenced, this does not definitely seem to be a "real" inheritance mechanism, but full autonomism of custom report module. The only question left for me would then be the one mentioned above - how to specify which data models the module may access. Could you, @David Bertha (or anybody else) clear up my mind regarding that?


//Edit:

Problem solved by only referencing to own module name and not the one of the model I wish to use data from in my report

1
Avatar
Annuleer
Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!

Maak vandaag nog een account aan om te profiteren van exclusieve functies en deel uit te maken van onze geweldige community!

Aanmelden
Gerelateerde posts Antwoorden Weergaven Activiteit
Model inheriance, how to override a default model in a module?
modules inheritance account.invoice model
Avatar
0
jan. 21
3519
How to get rid of the product name in account.invoice.line.name?
v8 modules invoice account.invoice account.invoice.line
Avatar
1
apr. 16
6527
how to overide abstract model method Opgelost
inheritance reporting
Avatar
1
dec. 22
2870
Inherit without changing original module
modules inheritance
Avatar
Avatar
Avatar
5
okt. 20
8155
Invoice report is displaying an incorrect value Opgelost
v8 reporting
Avatar
Avatar
Avatar
4
okt. 16
7348
Community
  • Tutorials
  • Documentatie
  • Forum
Open Source
  • Downloaden
  • Github
  • Runbot
  • Vertalingen
Diensten
  • Odoo.sh Hosting
  • Ondersteuning
  • Upgrade
  • Gepersonaliseerde ontwikkelingen
  • Onderwijs
  • Vind een boekhouder
  • Vind een partner
  • Word een Partner
Over ons
  • Ons bedrijf
  • Merkelementen
  • Neem contact met ons op
  • Vacatures
  • Evenementen
  • Podcast
  • Blog
  • Klanten
  • Juridisch • Privacy
  • Beveiliging
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo is een suite van open source zakelijke apps die aan al je bedrijfsbehoeften voldoet: CRM, E-commerce, boekhouding, inventaris, kassasysteem, projectbeheer, enz.

Odoo's unieke waardepropositie is om tegelijkertijd zeer gebruiksvriendelijk en volledig geïntegreerd te zijn.

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now