Pular para o conteúdo
Odoo Menu
  • Entrar
  • Experimente grátis
  • Aplicativos
    Finanças
    • Financeiro
    • Faturamento
    • Despesas
    • Planilhas (BI)
    • Documentos
    • Assinar Documentos
    Vendas
    • CRM
    • Vendas
    • PDV Loja
    • PDV Restaurantes
    • Assinaturas
    • Locação
    Websites
    • Criador de Sites
    • e-Commerce
    • Blog
    • Fórum
    • Chat ao Vivo
    • e-Learning
    Cadeia de mantimentos
    • Inventário
    • Fabricação
    • PLM - Ciclo de Vida do Produto
    • Compras
    • Manutenção
    • Qualidade
    Recursos Humanos
    • Funcionários
    • Recrutamento
    • Folgas
    • Avaliações
    • Indicações
    • Frota
    Marketing
    • Redes Sociais
    • Marketing por E-mail
    • Marketing por SMS
    • Eventos
    • Automação de Marketing
    • Pesquisas
    Serviços
    • Projeto
    • Planilhas de Horas
    • Serviço de Campo
    • Central de Ajuda
    • Planejamento
    • Compromissos
    Produtividade
    • Mensagens
    • Aprovações
    • Internet das Coisas
    • VoIP
    • Conhecimento
    • WhatsApp
    Aplicativos de terceiros Odoo Studio Plataforma Odoo Cloud
  • Setores
    Varejo
    • Loja de livros
    • Loja de roupas
    • Loja de móveis
    • Mercearia
    • Loja de ferramentas
    • Loja de brinquedos
    Comida e hospitalidade
    • Bar e Pub
    • Restaurante
    • Fast Food
    • Hospedagem
    • Distribuidor de bebidas
    • Hotel
    Imóveis
    • Imobiliária
    • Escritório de arquitetura
    • Construção
    • Administração de propriedades
    • Jardinagem
    • Associação de proprietários de imóveis
    Consultoria
    • Escritório de Contabilidade
    • Parceiro Odoo
    • Agência de marketing
    • Escritório de advocacia
    • Aquisição de talentos
    • Auditoria e Certificação
    Fabricação
    • Têxtil
    • Metal
    • Móveis
    • Alimentação
    • Cervejaria
    • Presentes corporativos
    Saúde e Boa forma
    • Clube esportivo
    • Loja de óculos
    • Academia
    • Profissionais de bem-estar
    • Farmácia
    • Salão de cabeleireiro
    Comércio
    • Handyman
    • Hardware e Suporte de TI
    • Sistemas de energia solar
    • Sapataria
    • Serviços de limpeza
    • Serviços de climatização
    Outros
    • Organização sem fins lucrativos
    • Agência Ambiental
    • Aluguel de outdoors
    • Fotografia
    • Aluguel de bicicletas
    • Revendedor de software
    Navegar por todos os setores
  • Comunidade
    Aprenda
    • Tutoriais
    • Documentação
    • Certificações
    • Treinamento
    • Blog
    • Podcast
    Empodere a Educação
    • Programa de educação
    • Scale Up! Jogo de Negócios
    • Visite a Odoo
    Obtenha o Software
    • Baixar
    • Comparar edições
    • Releases
    Colaborar
    • Github
    • Fórum
    • Eventos
    • Traduções
    • Torne-se um parceiro
    • Serviços para parceiros
    • Cadastre seu escritório contábil
    Obtenha os serviços
    • Encontre um parceiro
    • Encontre um Contador
    • Conheça um consultor
    • Serviços de Implementação
    • Referências de Clientes
    • Suporte
    • Upgrades
    Github YouTube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    Faça uma demonstração
  • Preços
  • Ajuda

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

  • CRM
  • e-Commerce
  • Financeiro
  • Inventário
  • PoS
  • Projeto
  • MRP
All apps
É necessário estar registrado para interagir com a comunidade.
Todas as publicações Pessoas Emblemas
Marcadores (Ver tudo)
odoo accounting v14 pos v15
Sobre este fórum
É necessário estar registrado para interagir com a comunidade.
Todas as publicações Pessoas Emblemas
Marcadores (Ver tudo)
odoo accounting v14 pos v15
Sobre este fórum
Ajuda

Why am I getting a mandatory field is not correctly error on this extended contracts code?

Inscrever

Seja notificado quando houver atividade nesta publicação

Esta pergunta foi sinalizada
inheritanceintegrityerrorcontractsodoo8.0
20 Respostas
19114 Visualizações
Avatar
Yenthe Van Ginneken (Mainframe Monkey)

Hi guys,

I've been extending the contracts from the sales module so that you can create contracts for cars (linking to fleet.vehicle). I've added the following fields to the model account.analytic.invoice.line:

class account_analytic_invoice_line(osv.osv): _inherit = 'account.analytic.invoice.line' _columns = { 'car_id': fields.many2one('fleet.vehicle', 'Car'), 'analytic_car_account_id': fields.many2one('account.analytic.account', 'Analytic Account 2'), 'car_license_plate': fields.text('Nummerplaat'), 'car_mavirent_nummer': fields.text('MaviRent nummer'), 'car_chassis': fields.text('Chassis'), 'car_rent_price': fields.float('Prijs'), 'car_number_of_units': fields.integer('Aantal'), 'car_line_tax_id': fields.many2many('account.tax', 'account_car_line_tax', 'car_line_id', 'tax_id', string='BTW', required=True), 'car_account_id': fields.many2one('account.account', 'Grootboekrekening', required=True), }


Then in the contract view I've added a new one2many (the field recurring_invoice_car_line_ids) like this:

<openerp> <data> <record id="view_contract_form_inherit_be_trans" model="ir.ui.view"> <field name="name">account.analytic.account.inherit</field> <field name="model">account.analytic.account</field> <field name="inherit_id" ref="account_analytic_analysis.account_analytic_account_form_form"/> <field name="arch" type="xml"> <xpath expr="//field[@name='recurring_invoice_line_ids']" position="after"> <label for="recurring_invoice_car_line_ids" attrs="{'invisible': [('recurring_invoices','=',False)]}"/> <div attrs="{'invisible': [('recurring_invoices','=',False)]}"> <field name="recurring_invoice_car_line_ids"> <tree string="Account Analytic Lines" editable="bottom"> <field name="car_id" on_change="car_id_change(car_id, car_license_plate, car_mavirent_nummer, car_chassis, car_rent_price)" attrs="{'required':[('car_id', '!=', '')]}"/> <!--These fields are only required when there is a value in the many2one field product_id' --> <field name="car_mavirent_nummer" attrs="{'required':[('car_id', '!=', '')]}"/> <field name="car_license_plate" attrs="{'required':[('car_id', '!=', '')]}"/> <field name="car_chassis" attrs="{'required':[('car_id', '!=', '')]}"/>

<field name="car_rent_price" attrs="{'required':[('car_id', '!=', '')]}"/> <field name="car_number_of_units" attrs="{'required':[('car_id', '!=', '')]}"/> <field name="car_line_tax_id" widget="many2many_tags"/> <field name="car_account_id"/> </tree> </field> </div> </xpath> </field> </record> </data> </openerp>

Now when a record is added on this one2many a Python function (on change event) named 'car_id_change' will go off which has the following code:

def car_id_change(self, cr, uid, ids, car, car_id=None,car_name='', car_license_plate='', car_mavirent_nummer='', car_chassis='', car_rent_price=0.0,car_number_of_units=1.0, context=None): context = context or {} local_context = dict(context, car_id=car_id) result = {} if not car: return {'value': {'car_name': '', 'car_license_plate': '', car_mavirent_nummer: '', car_chassis: '','car_rent_price': 0.0, 'car_number_of_units': 1.0}} else: res = self.pool.get('fleet.vehicle').browse(cr, uid, car, context=local_context) if res['license_plate']: car_license_plate = res['license_plate'] if res['name']: car_name = res['name'] if res['MaviVoertuigNummer']: car_mavirent_nummer = res['MaviVoertuigNummer'] if res['Chassis']: car_chassis = res['Chassis'] #Get a tax to automatically add to the contract. btw_categ_pool = self.pool.get('account.tax') goede_btw_id = btw_categ_pool.search(cr, uid, [('description','=','VAT-OUT-21-S')]) result.update({'car_name': car_name,'car_license_plate': car_license_plate, 'car_mavirent_nummer': car_mavirent_nummer, 'car_chassis': car_chassis, 'car_rent_price': car_rent_price, 'car_number_of_units': car_number_of_units, 'car_line_tax_id': [(6, 0, goede_btw_id)]}) res_final = {'value':result} return res_final

Which works fine. I can choose cars and all the data is filled in automatically (atleast, which I can).
When I now click on save I get an error though:

Integrity Error

The operation cannot be completed, probably due to the following: - deletion: you may be trying to delete a record while other records still reference it - creation/update: a mandatory field is not correctly set [object with reference: name - name]

When I look in the terminal I will see the following:

openerp.sql_db: bad query: INSERT INTO "account_analytic_invoice_line" ("id", "car_mavirent_nummer", "car_license_plate", "car_account_id", "car_number_of_units", "car_chassis", "analytic_car_account_id", "car_rent_price", "car_id", "quantity", "create_uid", "write_uid", "create_date", "write_date") VALUES(nextval('account_analytic_invoice_line_id_seq'), 'MAV09', 'FFF-111', 819, 1, 'OPO06', 13, 0.0, 2, 1.0, 1, 1, (now() at time zone 'UTC'), (now() at time zone 'UTC')) RETURNING id

Traceback (most recent call last): File "/odoo/odoo-server/openerp/sql_db.py", line 234, in execute res = self._obj.execute(query, params) IntegrityError: null value in column "name" violates not-null constraint DETAIL: Failing row contains (27, null, 1, 2016-01-13 08:48:12.818483, null, null, 1, null, 2016-01-13 08:48:12.818483, 1, null, MAV09, 13, FFF-111, 1, OPO06, 819, 0, 2).


I do see there is a null value in the SQL statement and I know that is not allowed but what I don't know is where it is coming from or what I am missing that it is giving null. I'm passing along all the values if I'm not mistaking? So, how do I fix this?

Update: The error was coming from the fact that I didn't inherit the module 'account', I did inherit 'account_analytic_analysis' but not 'account'. I now have a new issue:

Integrity Error The operation cannot be completed, probably due to the following: - deletion: you may be trying to delete a record while other records still reference it - creation/update: a mandatory field is not correctly set [object with reference: price_unit - price.unit]


You can view and test the whole module, which is available on Github: https://github.com/Yenthe666/Dev/tree/master/aa_maatwerk_be_trans

Thanks,
Yenthe

2
Avatar
Cancelar
Temur

what are steps to reproduce for an updated issue?

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Temur go to sales > contracts, create a new contract and add one car and no products. Then click on save, you will get a notification saying that a field is missing. When you click on save again you will get the error.

Axel Mendoza

not solved yet?

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Axel sadly no! I can't find the problem in the code.

Temur

Ok. I reproduced it

Temur

@Yenthe, I traced down the error and applied quick fix to be able to save contract according of steps to reproduce above. Please refer to updated answer and adapt solution further to meet your requirements.

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Temur perfect! That was exactly what I was looking for. I'll need some minor changes to have everything perfect but my problem is fixed now. Thanks a lot! Accepted & upvoted! :)

Avatar
Temur
Melhor resposta

Try it please:

....
    goede_btw_id = btw_categ_pool.search(cr, uid, [('description','=','VAT-OUT-21-S')])
    if type(goede_btw_id) in (long, int,):
        browse_ids = [goede_btw_id]
    else:
        browse_ids = goede_btw_id
    for godie_btw_obj in btw_categ_pool.browse(cr, uid, browse_ids, context=context):
        if not goede_btw_obj.name:
            goede_btw_obj.name = goede_btw_obj.description
    result.update({'car_name': car_name,'car_license_plate': car_license_plate, 'car_mavirent_nummer': car_mavirent_nummer, 'car_chassis': car_chassis, 'car_rent_price': car_rent_price, 'car_number_of_units': car_number_of_units, 'car_line_tax_id': [(6, 0, goede_btw_id)]})
....


UPDATE:

'account' is in dependency list, but I've got "IntegrityError: null value in column "name" violates not-null constraint" anyway. this error were originated from missing mandatory field "name" in "account_analytic_invoice_line" object, I fixed it in place by replacing required=True to required=False... I.e. if it meant not to be required, it should be fixed as follows:


class account_analytic_invoice_line(models.Model):
    _inherit = "account.analytic.invoice.line"

name = fields.Text(required=False) 

this way "IntegrityError: null value in column "name" violates not-null constraint" error is gone away, as we made it not mandatory field by required=False incremental update.


But I've got next error, same as in question post: "IntegrityError: null value in column "price_unit" violates not-null constraint". This error were originated from "price_unit" field set as mandatory but not displayed in a form view. here we can apply two solutions, either add back to the view all mandatory fields, or make them not mandatory same as for the "name" field above. Then I've got more errors of same kind: "IntegrityError: null value in column "uom_id" violates not-null constraint", followed by: "IntegrityError: null value in column "product_id" violates not-null constraint"...  Just as a quick fix I've added this fields back to the Form View and finally I was able to save the contract without errors. Here is an xml with mandatory fields in place:


<record id="view_contract_form_inherit_be_trans" model="ir.ui.view">
<field name="name">account.analytic.account.inherit</field>
<field name="model">account.analytic.account</field>
<field name="inherit_id" ref="account_analytic_analysis.account_analytic_account_form_form"/>
<field name="arch" type="xml">
<!-- Make the date fields required -->
<xpath expr="//field[@name='date_start']" position="replace">
<field name="date_start" required="True"/>
</xpath>
<xpath expr="//field[@name='date']" position="replace">
<field name="date" required="True"/>
</xpath>
<xpath expr="//field[@name='recurring_invoice_line_ids']" position="after">
<label for="recurring_invoice_car_line_ids" attrs="{'invisible': [('recurring_invoices','=',False)]}"/>
<div attrs="{'invisible': [('recurring_invoices','=',False)]}">
<field name="recurring_invoice_car_line_ids">
<tree string="Account Analytic Lines" editable="bottom">
<field name="car_id" on_change="car_id_change(car_id, car_license_plate, car_mavirent_nummer, car_chassis, car_rent_price)" attrs="{'required':[('car_id', '!=', '')]}"/>
<!--These fields are only required when there is a value in the many2one field product_id' -->
<field name="car_mavirent_nummer" attrs="{'required':[('car_id', '!=', '')]}"/>
<field name="car_license_plate" attrs="{'required':[('car_id', '!=', '')]}"/>
<field name="car_chassis" attrs="{'required':[('car_id', '!=', '')]}"/>
<field name="car_rent_price" attrs="{'required':[('car_id', '!=', '')]}"/>
<field name="car_number_of_units" attrs="{'required':[('car_id', '!=', '')]}"/>
<field name="car_line_tax_id" widget="many2many_tags"/>
<field name="uom_id" />
<field name="product_id" />
<field name="price_unit" />

<field name="car_account_id"/>
</tree>
</field>
</div>
</xpath>
</field>
</record>


Now it's possible to go to sales > contracts, create a new contract and add one car and no products, then click on save and no errors, you can save it successfully. However the above changes are a quick fix, I've not investigated application logic deeper, please adapt solution to your case. For each mandatory field, either add them in the view or make them optional (NOT required) fields as I made optional the "name" field above, and/or review dependency list of your module again if it may change a behavior of your module, as other modules may change fields by incremental updates as well.






1
Avatar
Cancelar
Yenthe Van Ginneken (Mainframe Monkey)
Autor

Thanks Temur but I was just missing the 'account' import, I only had 'account_analytic_analysis' and not 'account' and this was giving the strange error. I've updated my question since I now have another strange one.

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Temur: I've decided to put it on Github so you can see all the code and test it if you'd like / need to. See https://github.com/Yenthe666/Dev/tree/master/aa_maatwerk_be_trans

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Temur perfect! That was exactly what I was looking for. I'll need some minor changes to have everything perfect but my problem is fixed now. Thanks a lot! Accepted & upvoted! :)

Temur

You're welcome

Avatar
Axel Mendoza
Melhor resposta

@Yenthe, i'm with Pawan on his answer, I don't think that converting the required field into non-required is a good idea, maybe doing that you end up getting broken another scenario.

For me better you follow what it's done on the model account.analytic.account on the method on_change_template building the values for the field recurring_invoice_line_ids, specifically this:

...

invoice_line_ids = []

for x in template.recurring_invoice_line_ids:

invoice_line_ids.append((0, 0, {

'product_id': x.product_id.id,

'uom_id': x.uom_id.id,

'name': x.name,

'quantity': x.quantity,

'price_unit': x.price_unit,

'analytic_account_id': x.analytic_account_id and x.analytic_account_id.id or False,

}))

res['value']['recurring_invoices'] = template.recurring_invoices

res['value']['recurring_interval'] = template.recurring_interval

res['value']['recurring_rule_type'] = template.recurring_rule_type

res['value']['recurring_invoice_line_ids'] = invoice_line_ids

...

Using this solution in your own onchange you need to add the needed fields that @Temur found that need to have a value in your editable tree, at least with invisible="1" so the onchange values could fill those fields and they will be sent to the model create/write and you will don't end up with errors for not-null fields
 

1
Avatar
Cancelar
Avatar
Pawan
Melhor resposta

Yenthe,

There is  a predefined fields called 'name' in account_analytic_invoice_line object which is mandatory by default, which you are not defining while returning it from on change of car field.

So adding {'name': "SOME DATA"} to the returning dictionary from the function.

Regards,

 




0
Avatar
Cancelar
Yenthe Van Ginneken (Mainframe Monkey)
Autor

Thanks for the reply Pawan! I was thinking that to initially so at some point I added a name field in the dict but even then I get this error. An example: result.update({'car_name': car_name,'car_license_plate': car_license_plate, 'car_mavirent_nummer': car_mavirent_nummer, 'car_chassis': car_chassis, 'car_rent_price': car_rent_price, 'car_number_of_units': car_number_of_units, 'car_line_tax_id': [(6, 0, goede_btw_id)], 'name': 'Demo name'})

Temur

What about 'name' field in 'account.tax' object (in the goede_btw_id one) ? it's defined as mandatory as well

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Pawan and @Temur problem seem to came from the fact that I didn't inherit 'account', I had inherited 'account_analytic_analysis' but missed 'account'. I've updated my question since I now have a new issue about [object with reference: price_unit - price.unit]

Pawan

Yenthe,
price_unit also exist in "account_analytic_invoice_line", try adding {'price_unit':0.0} too in your code, and you are returning dictionary at 2 places, please confirm with both the scenarios because i can't find any other scenario for this error

Yenthe Van Ginneken (Mainframe Monkey)
Autor

Pawan, That was exactly my idea too but that doesn't work either. I'll keep getting the error regarding price_unit..

Yenthe Van Ginneken (Mainframe Monkey)
Autor

@Pawan and @Temur: I've decided to put it on Github so you can see all the code and test it if you'd like / need to. See https://github.com/Yenthe666/Dev/tree/master/aa_maatwerk_be_trans

Está gostando da discussão? Não fique apenas lendo, participe!

Crie uma conta hoje mesmo para aproveitar os recursos exclusivos e interagir com nossa incrível comunidade!

Inscreva-se
Publicações relacionadas Respostas Visualizações Atividade
How to inherit / modify point of sale pages & create restrictions? Resolvido
inheritance point_of_sale odoo8.0
Avatar
Avatar
1
nov. 21
7997
How to inherit calendar popup? Resolvido
inheritance popup odoo8.0
Avatar
6
fev. 21
16275
how to inherit the timesheet view in my new modul.
modules inheritance odoo8.0
Avatar
1
jun. 16
4153
In odoo 8 Contracts Form Check Date constraints method gets triggered even after providing valid input dates. How to fix this?
constraint contracts odooV8 odoo8.0
Avatar
0
abr. 19
4992
How to add field to One2Many with xpath expressions? Resolvido
inheritance one2many xpath odoo8.0
Avatar
Avatar
1
abr. 15
14414
Comunidade
  • Tutoriais
  • Documentação
  • Fórum
Open Source
  • Baixar
  • Github
  • Runbot
  • Traduções
Serviços
  • Odoo.sh Hosting
  • Suporte
  • Upgrade
  • Desenvolvimentos personalizados
  • Educação
  • Encontre um Contador
  • Encontre um parceiro
  • Torne-se um parceiro
Sobre nós
  • Nossa empresa
  • Ativos da marca
  • Contato
  • Empregos
  • Eventos
  • Podcast
  • Blog
  • Clientes
  • Legal • Privacidade
  • Segurança
الْعَرَبيّة 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 é um conjunto de aplicativos de negócios em código aberto que cobre todas as necessidades de sua empresa: CRM, comércio eletrônico, contabilidade, estoque, ponto de venda, gerenciamento de projetos, etc.

A proposta de valor exclusiva Odoo é ser, ao mesmo tempo, muito fácil de usar e totalmente integrado.

Site feito com

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