- Mailing Lists
- web
- [9.0/10.0 QWeb] Is it Possible To Use 'attrs=' to Show/Hide Form View Elements Populated From a Boolean in a One2many?
web mailing list archives
web@odoo-community.org
Browse archives
- By thread
-
By date
- October 2024 2
- September 2024 5
- August 2024 1
- July 2024 1
- June 2024 2
- May 2024 7
- April 2024 4
- March 2024 3
- February 2024 2
- January 2024 1
- November 2023 3
- September 2023 5
- August 2023 4
- July 2023 3
- June 2023 1
- April 2023 1
- March 2023 7
- January 2023 2
- December 2022 1
- November 2022 3
- June 2022 2
- May 2022 2
- March 2022 1
- February 2022 2
- December 2021 1
- November 2021 8
- October 2021 2
- September 2021 1
- August 2021 12
- July 2021 9
- June 2021 8
- May 2021 20
- April 2021 31
- March 2021 7
- February 2021 1
- January 2021 6
- December 2020 12
- November 2020 29
- October 2020 5
- August 2020 1
- July 2020 28
- June 2020 14
- May 2020 7
- April 2020 10
- February 2020 9
- January 2020 5
- November 2019 1
- September 2019 2
- July 2019 5
- March 2019 4
- December 2018 6
- October 2018 38
- September 2018 20
- August 2018 19
- April 2018 1
- March 2018 1
- January 2018 1
- December 2017 1
- August 2017 1
- April 2017 1
- December 2016 2
- October 2016 1
- September 2016 1
4 experience for racks
Fwd: Why JavaScript like “owl.carousel” does not work in Odoo 10 web template?
[9.0/10.0 QWeb] Is it Possible To Use 'attrs=' to Show/Hide Form View Elements Populated From a Boolean in a One2many?
by
odoocommunitywidgets
Hi Community,
I'm working on a project that requires 'configurable' forms for different document types (eg. similar to /sale-workflow/sale_order_types, with many different fields shown/hidden based on a one2many show/hide boolean configuration table).
I'm working on a project that requires 'configurable' forms for different document types (eg. similar to /sale-workflow/sale_order_types, with many different fields shown/hidden based on a one2many show/hide boolean configuration table).
I have seen examples in Odoo core of configurable visibility of form fields, groups, etc. based on a selection field (eg. Delivery Methods > Price Computation > Selection Radio Buttons). In my case however it is useful to have a one2many relationship (eg. like sortable order lines) with a boolean field inside for visibility (ie. visible = yes/no).
Pushing the same concept a little further, if possible I would like to apply the same (visible = yes/no) options to <label>, <group>, <page>, <notebook>, <div>, and so on, to allow for configurable formatting of form layouts.
I'm a little stumped on how to achieve this, has anyone else encountered this scenario and found a solution?
Regards,
Luke Branch
Luke Branch