← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 753133] [NEW] Wrong default address of employee

 

Public bug reported:

OpenERP V6.0.1 and V6.0.2
login as a user not admin
when Create employee, get following error:

Traceback (most recent call last): File "netsvc.pyo", line 489, in
dispatch File "service\web_services.pyo", line 599, in dispatch File
"osv\osv.pyo", line 122, in wrapper File "osv\osv.pyo", line 176, in
execute File "osv\osv.pyo", line 167, in execute_cr File "osv\orm.pyo",
line 973, in default_get File "d:\OpenERP 6.0\Server\addons\hr\hr.py",
line 194, in <lambda> File "osv\orm.pyo", line 287, in __getattr__
AttributeError: 'Field partner_id not found in
browse_record(res.partner.address, 4)'

read the source and found this :
'address_id': lambda self,cr,uid,c: self.pool.get('res.partner.address').browse(cr, uid, uid, c).partner_id.id

what is the logic you were trying to implement?

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/753133

Title:
  Wrong default address of employee

Status in OpenERP Modules (addons):
  New

Bug description:
  OpenERP V6.0.1 and V6.0.2
  login as a user not admin
  when Create employee, get following error:

  Traceback (most recent call last): File "netsvc.pyo", line 489, in
  dispatch File "service\web_services.pyo", line 599, in dispatch File
  "osv\osv.pyo", line 122, in wrapper File "osv\osv.pyo", line 176, in
  execute File "osv\osv.pyo", line 167, in execute_cr File
  "osv\orm.pyo", line 973, in default_get File "d:\OpenERP
  6.0\Server\addons\hr\hr.py", line 194, in <lambda> File "osv\orm.pyo",
  line 287, in __getattr__ AttributeError: 'Field partner_id not found
  in browse_record(res.partner.address, 4)'

  read the source and found this :
  'address_id': lambda self,cr,uid,c: self.pool.get('res.partner.address').browse(cr, uid, uid, c).partner_id.id

  what is the logic you were trying to implement?



Follow ups

References