fields.reference browse

[Frédéric (Ferme du Sart)]

- browsing a fields.reference returns an 'object,id' string instead of browsing into record
- one2many should accept a fields.reference field as _fields_id

[Nicolas DS (zyphos)]

- The aim of browsing is... browsing. To retrieve the id simply use <reference_field_name>.id
- It's not the aim of a one2many field.
I think that you have a misconception in your project.
What are you trying to do ? Or what kind of relation are you seeking ?
Many2many ?

I am also working on a super many2many relation (many2many between any kind of resource).
https://blueprints.launchpad.net/openobject-server/+spec/many-resource2one

[Joël Grand-Guillaume @ camptocamp (jgrandguillaume-c2c)]

Hi !

I agree with Nicolas DS.

Regards,

[Frédéric (Ferme du Sart) (frederic-declercq)]

Nicolas DS:
"The aim of browsing is... browsing. To retrieve the id simply use <reference_field_name>.id"

We can't do it. When browsing, we have to do:
res_mode, res_id = <reference_field_name.split(',')
res_id = long(res_id)
res = self.pool.get(res_model).browse(cr, uid, res_id, context=context)

This problem has been exposed to OpenERP team last week. Olivier (Domy???) has asked to OpenERP coders, then answered me that it was a real bug to transmit.

I've coded the corrective on https://code.launchpad.net/~frederic-declercq/openobject-server/server-fu-reference_browse. This BUG was just created to explain correction.

During the corrective, I saw that browsing references allows using fields.related based on reference. And few code lines allowed to use reference as one2many.

ie:
- Treasury (money) can come from sale.order, pos.order, account.invoice, purchase.order (diposit)... payments made can be linked to any resource by having field.reference on account.treasury.line, and treasury_ids on destinations.
- Product/partner/supplierinfo special fields (vintage, microbiotics, caliber, origin, EC number...) may be usefull for some products/partners... but not for an HR product (hour for an employee). Specifications required fields can be created depending on product's category and seen in a one2many list to complete, stored in a products specification table, but editable into objects views (product/partner/supplierinfo...)

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Fredric,

Would you please demonstrate a module which uses this facilty?

And a point to note, the one2many should NEVER accept a fields.reference field as _fields_id.

Thanks.

[Olivier Dony (Odoo) (odo-openerp)]

Browsing through reference fields has been implemented in v6 and was already released in 6.0 RC1 I think, marking as Fix Released.

For the second point, using a reference field instead of a many2one as the implementation for a one2many (i.e _fields_id) is not acceptable, as the database can't maintain the integrity of the foreign keys. If you really need this you must implement the one2many yourself with a function field or by inheriting fields.one2many, but we won't allow this in the core ORM, it introduces too many potential issues.

Thanks!