Hide fields in a form in edit-mode as it is possible for view-mode

[Daniel Hammerschmidt]

It is possible to hide fields in a form while viewing (e.g. the partner's field 'is_company'). It would be fine if it is possible to hide fields that easy while editing (e.g. a computed one2many-list).

This simply requires an extension to the selector-list of the cass-rule for oe_edit_only (see attaachment).

[Amit Bhavsar (Open ERP) (amb-openerp)]

Hello Daniel,

I have checked your Issue, But It's ambiguous to us. So Would you please elaborate more. and It's batter for us If you provide step for reproduce.

Thank you and waiting for your reply!

[Stefan Rijnhart (Opener) (stefan-opener)]

I'd favour this. In fact a customer requested this exact feature for a view that contains a large number of unwritable function fields. In write mode, this view looks like a large grey slab dotted with a small number of writeable fields. We want to be able to hide the unwriteable fields in write modus.

Therefore, setting to confirmed.

[Daniel Hammerschmidt (redneck)]

Hello,

the following is a snippet from the form view architecture for res.partner (base.view_partner_form):

                    <div class="oe_title">
                        <div class="oe_edit_only">
                            <label for="name"/> (
                            <field name="is_company" on_change="onchange_type(is_company)" class="oe_inline"/> <label for="is_company" string="Is a Company?"/>)
                        </div>
                      ...
                    </div>

The label for the name field and the field is only visible while editing the record.

I added a functional field of type one2many to the res.partner model which is read-only, but there is a "real" field which the computation is based on and therefore it is editable. So, I want to hide the computed field while editing and the "real" field while viewing the record as in the following snippet.

          <div class="oe_view_only oex_kanban_table oex_as_fields">
            <field name="all_commchannel_ids" nolabel="1" mode="kanban" context="{'active_partner_id': active_id}">
              ...
            </field>
          </div>
          <div class="oe_edit_only">
            <label string="Communication" class="oe_horizontal_separator"/>
            <field name="commchannel_ids" nolabel="1" mode="tree"
              context="{'default_partner_id': active_id, 'active_test': False}">
              ...
            </field>
          </div>

To get this running I added ".openerp .oe_form_editable .oe_view_only" to the selector list or the css-rule for ".oe_edit_only".

[Paramjit Singh Sahota(OpenERP) (psa-openerp)]

Hello Daniel Hammerschmidt,

I have checked your scenario, but this is not a bug but its your suggestion for improvement.
It's good Implementation as per the usability point of view. So We can consider this is as your suggestion and considering it as a "Wishlist".

Thanks for the reporting!

[Lionel Sausin - Initiatives/Numérigraphe (ls-initiatives)]

I've tested the attached patch in v7.0 and it works for me. I pushed a branch and MP for OCB.

[Lionel Sausin - Initiatives/Numérigraphe (ls-initiatives)]

This won't fit the OCB strategy, so I moved the 7.0 branch to openobject-addons for the sake of clarity: it merges into the official 7.0 as well as OCB.
 I'm going to propose a merge directly into the trunk.

[Lionel Sausin - Initiatives/Numérigraphe (ls-initiatives)]

Looks like this is fixed in the trunk already: please check out revid:<email address hidden>
The style is named "or_read_only", not "or_view_only" as we proposed.

[Lionel Sausin - Initiatives/Numérigraphe (ls-initiatives)]

I meant to write: "oe_read_only"

[Stefan Rijnhart (Opener) (stefan-opener)]

@Lionel good to hear. Thanks for your work!

[Lionel Sausin - Initiatives/Numérigraphe (ls-initiatives)]

Since this is in trunk now, maybe we can allow a backport.