Skip to Content

Contributors

Re: Best practice add optional="show" when adding fields in tree views

Thanks Pedro, we are in complete agreement then.


Regards, Ronald


Op 29-08-2023 om 10:42 schreef Pedro M. Baeza:

> Sorry, my bad. I don't know why, I read optional="hide". It's OK to 

> put optional="show", but I would leave out of the equation mandatory 

> fields without default, or those protected with a group, as the group 

> is already the filtering method for not showing them.

>

> Regards.

>

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 

> <https://odoo-community.org/groups/contributors-15>

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe 

> <https://odoo-community.org/groups?unsubscribe>

>

by "Ronald Portier" <rportier@therp.nl> - 11:01 - 29 Aug 2023

Reference

  • Best practice add optional="show" when adding fields in tree views

    Hello Contributors!

     

    I love to have your opinions here.

     

    I would recommend to PSC to review when migrating modules to ask authors for adding -> optional="show" <- to the fields they add. In order to be possible to hide.

     

    This is our sale-workflow runbot talking about sale order lines (NOTE: in v16!! In v15 is simply impossible to test anything without uninstalling 12-15 modules to have something we can call “VIEW” 😃 )

     

     

    This is the best we could have.

     

     

    Fields that cannot be hidden:

     

    • Sequence2
    • Lot_id
    • Elaborations_ids
    • Elaboration_note

     

    This best practice could apply to sale.order.lines, and all the lines in general, lis invoice lines, stock picking lines, etc…

     

    Has it any sense for you?

     

    Best regards,

    Rafael Blasco

    Moduon Team

     


    by Rafael Blasco (Moduon) - 06:50 - 28 Aug 2023