sale/stock_view.xml - conceptual error

[Ferdinand]

in this file sale_id is added to the view after "active" - but it never gets displayed (V5 and V6) (because of no field active in the view?)

if it is displayed - which is important to be able to navigate back from picking to SO - IMHO the field "Origin" can be eliminated

[Ferdinand (office-chricar)]

please check also for procurements

[Nhomar - Vauxoo (nhomar)]

Im Agree with you, but, the field "Origin" is useful in some cases, we use
this field in a lot of functions,

Regards

2010/7/3 Ferdinand @ ChriCar <email address hidden>

> Public bug reported:
>
> in this file sale_id is added to the view after "active" - but it never
> gets displayed (V5 and V6) (because of no field active in the view?)
>
> if it is displayed - which is important to be able to navigate back from
> picking to SO - IMHO the field "Origin" can be eliminated
>
> ** Affects: openobject-addons
> Importance: Undecided
> Status: New
>
> --
> sale/stock_view.xml - conceptual error
> https://bugs.launchpad.net/bugs/601485
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenObject Addons.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> in this file sale_id is added to the view after "active" - but it never
> gets displayed (V5 and V6) (because of no field active in the view?)
>
> if it is displayed - which is important to be able to navigate back from
> picking to SO - IMHO the field "Origin" can be eliminated
>
>
>

--
Saludos Cordiales

Nhomar G. Hernandez M.
[phone]
[phone]
[phone] ext 124
[phone]
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.netquatro.com
Linux-Counter: 467724
Correos:
<email address hidden>
<email address hidden>

[Ferdinand (office-chricar)]

@ Nhomar:
OK - but shouldn't it then be called differently ?

[Nhomar - Vauxoo (nhomar)]

Well. With this option i'm agree (for version 6), but IMHO the function
should be the same "__fill automatcally tracing all process about a
document__" the "Link" as ferdinand says is the correct way.

2010/7/3 Ferdinand @ ChriCar <email address hidden>

> @ Nhomar:
> OK - but shouldn't it then be called differently ?
>
> --
> sale/stock_view.xml - conceptual error
> https://bugs.launchpad.net/bugs/601485
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenObject Addons.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> in this file sale_id is added to the view after "active" - but it never
> gets displayed (V5 and V6) (because of no field active in the view?)
>
> if it is displayed - which is important to be able to navigate back from
> picking to SO - IMHO the field "Origin" can be eliminated
>
>
>

--
Saludos Cordiales

Nhomar G. Hernandez M.
[phone]
[phone]
[phone] ext 124
[phone]
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.netquatro.com
Linux-Counter: 467724
Correos:
<email address hidden>
<email address hidden>

[Amit Parik (amit-parik)]

Hello DR Ferdinand,

In version5.0 "active" field in "Extended View". So you can add group "Extended View" in related user then you can see the "sale_id" and "active" both field in "Others info" tab.

In version6.0 "active" field use as a "auto_picking" name and this field is in "Multi Company" and "Extended" View. So for that you have to install the "multi_company" module and add "Multi Company" and "Extended" both groups in the related users. Now You can see "sale_id" and "active" both field in "Additional info" tab.

Thanks.

[Ferdinand (office-chricar)]

well problem described in the initial report is "solved" by

                <field name="auto_picking" position="after">
                    <field name="sale_id"/>

instead of
                <field name="acitve" position="after">
                    <field name="sale_id"/>

nevertheless I am not sure if the rule described in #5 is the correct way to do
Example:
* field A is only visible for "Extended"
* field B should be placed after A, but visible for all

What AMP is saying is that B is only visible for group "Extended" which IMHO is not correct.
at least it might create unwanted side effects as it is very difficult to find the inheriting views and it shouldn't be the job of the maintainer of field A to tell the maintainer of field B that he has added an attribute "Extended" and hence B must be placed elsewhere to be displayed.

IMHO inheritance and display logic must be completely separated.

[qdp (OpenERP) (qdp)]

Hello,
Thank you for your suggestion! However this is unfortunately out of the scope of the current OpenERP release, so we cannot implement it.
Let's close this bug for now, for the sake of clarity in Launchpad, it can always be reopened later when we consider new features for future roadmaps.
Thank you for your understanding!