OpenChatter Multicompany environment cant add followers

Bug #1225146 reported by OscarAlca on 2013-09-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Low
OpenERP Publisher's Warranty Team

Bug Description

When adding followers in the main company there is no problem, but when switching company and trying to add new followers to any document it gives the same message that the old world famous multicompany bug ( partner operation read )

here is a video explainig itself better than me.

http://www.youtube.com/watch?v=1vCAn00f2AY&feature=youtu.be

Related branches

Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
OscarAlca (oscarolar) on 2013-09-17
description: updated

Hi,

The root cause of this issue lies in the demo data created while installing the module "multi_company", that is, the company assigned to the contacts are not the same as of it's parent partner(with "is_company = True").

For example, the partner ASUStek(is_company True) is set to work for "OpenERP US" company and it's contacts, "Joseph Walters" and "Tang Tsui" are set to work for "Your Company", this is wrong configuration, every contact should be in the same company as their owning company.

The record rule for "res.partner" object shows the partners from the ancestors and descendants companies(or company-less) and as the "ASUStek" is itself is not accessible hence the contacts belonging to it wont be accessed and hence resulting into this warning when accessed by the user of the company "Odoo".

I have fixed the demo data by assigning the correct company in the branch lp:~openerp-dev/openobject-addons/7.0-opw-597936-rgo

Currently, this branch is under review of our experts, once it gets their approval it will be merged with main stable.

Thanks.

Changed in openobject-addons:
importance: Undecided → Low
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers