openerp-community-reviewer team mailing list archive

["Martin Trigaux \(OpenERP\)" <mat@xxxxxxxxxxx>]

Hello,

Indeed this was an error, thanks for the report and the merge proposal.
We have merged it into server 7.0

revno: 5248 [merge]
revision-id: mat@xxxxxxxxxxx-20140226133716-vgdjjmqc2lou0n3u

Regards


** Changed in: openobject-server
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of OpenERP
Community Backports Team, which is subscribed to OpenERP Community
Backports (Server).
https://bugs.launchpad.net/bugs/1194893

Title:
  Export creates xml id based on wrong table name

Status in OpenERP Community Backports (Server):
  Fix Released
Status in OpenERP Community Backports (Server) 7.0 series:
  Fix Released
Status in OpenERP Server:
  Fix Released

Bug description:
  When exporting many2one fields, _get_xml_id crafts an xml id using the
  table name of the exported model, not of the many2one model.

  For instance, when exporting a partner's receivable account, the
  ir_model_data entry of an account with database id 659 looks like
  this:

         name        | res_id |    model    
  -------------------+--------+-------------
   res_partner_659_1 |    659 | res.partner

  Because the model from this table is ignored at import time, the xml
  id can actually be reused. But meanwhile, the integrity of the table
  is broken because there is no partner with id 659. And it looks bad in
  the export file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ocb-server/+bug/1194893/+subscriptions