On 10/04/13 17:06, Maxime Chambreuil (http://www.savoirfairelinux.com)
wrote:
> One drawback of the child_of approach is with third-party integration.
> If you access OpenERP database to synchronize data with third-party
> software or for reporting purposes, you will need to reimplement the
> child_of logic.
>
I don't understand your point ?
On:
Camptocamp Holding
Camptocamp CH
Camptocamp FR
Joel
If I do a claim for C2C CH, this claim does NOT belong to C2C holding. It's
normal that, on claim_ids for C2C Holding, I do not have the claim to
C2C CH.
What I said is that we have a UI feature in the web client allowing to get
claims of Camptocamp Holding and all it's subsidiaries.
IMHO, the behaviour is the same for Joël and Camptocamp.
Child_of is just a UI tool for searching inside a whole company or group.
Even if you want to develop a UI tool that has the same feature than the
web client, you do not need to implement child_of, you just pass a domain
with child_of in your RPC call.
On 10/04/13 17:06, Maxime Chambreuil (http:// www.savoirfaire linux.com)
wrote:
> One drawback of the child_of approach is with third-party integration.
> If you access OpenERP database to synchronize data with third-party
> software or for reporting purposes, you will need to reimplement the
> child_of logic.
>
I don't understand your point ?
On:
Camptocamp Holding
Camptocamp CH
Camptocamp FR
Joel
If I do a claim for C2C CH, this claim does NOT belong to C2C holding. It's
normal that, on claim_ids for C2C Holding, I do not have the claim to
C2C CH.
What I said is that we have a UI feature in the web client allowing to get
claims of Camptocamp Holding and all it's subsidiaries.
IMHO, the behaviour is the same for Joël and Camptocamp.
Child_of is just a UI tool for searching inside a whole company or group.
Even if you want to develop a UI tool that has the same feature than the
web client, you do not need to implement child_of, you just pass a domain
with child_of in your RPC call.
Fabien