purchase_analytic_plan XML view error
purchase_
seems to contain invalid code :
<!-- Replace analytic_id with analytics_id in account.
<record model="ir.ui.view" id="invoice_
<field name="name"
<field name="model"
<field name="inherit_id" ref="account.
<field name="priority"
<field name="arch" type="xml">
<field name="account_
</field>
</record>
comment implies account.
the actual code tries to update account.invoice.
analytics_id exists on account.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- 2013-12-20
- Last reply:
- 2013-12-20
This question was originally filed as bug #1263218.
D Verhelst (dimitriverhelst) said : | #1 |
purchase_
seems to contain invalid code :
<!-- Replace analytic_id with analytics_id in account.
<record model="ir.ui.view" id="invoice_
<field name="name"
<field name="model"
<field name="inherit_id" ref="account.
<field name="priority"
<field name="arch" type="xml">
<field name="account_
</field>
</record>
comment implies account.
the actual code tries to update account.invoice.
analytics_id exists on account.
Dimitri,
There actually is no problem with any xml part here.
The xml record inherits the Invoice model for changing the analytic, because the invoice lines are inline.
From the xml arch,the field field is found inside the invoice line, so that will be replaced as per the new xml.
Did you encounter any traceback or unnecessary behavior on the view?
Hope this helps.
Thanks.
D Verhelst (dimitriverhelst) said : | #3 |
Hi SCS,
When upgrading a database from 7.0 beta to current LTS release I encounter the following error:
Could it be that the upgrade functionality doesn't understand inline inheritance ?
except_orm: ('View error', u"Can't find field 'analytics_id' in the following view parts composing the view of object model 'account.
2013-12-20 19:28:01,485 13989 ERROR tlt_live1 openerp.
<record model="ir.ui.view" id="invoice_
<field name="name"
<field name="model"
<field name="inherit_id" ref="account.
<field name="priority"
<field name="arch" type="xml">
<field name="account_
</field>
</field>
</record>
Dimitri,
Its not so.
One possbility is, you have a custom module and its installed prior to purchase_
And, I still believe it should better be Xpath to be used for the field operations on inheritance of view.
Thanks.
Thibault Duverger (tduverger) said : | #5 |
I Have the same problem
How can i solve it?
Can you help with this problem?
Provide an answer of your own, or ask D Verhelst for more information if necessary.