<img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> <a name="product-attribute-group"></a> <h2>Product Attribute Group</h2> <p>This module was written to extend the functionality of product attributes to support grouping attributes and allow you to choose a group of attributes when creating a product rather than one at a time while giving as much flexibility as possible. This saves having to manually add many attributes to products, and also allows by just updating a single group to update all products using that group.</p> <a name="installation"></a> <h2>Installation</h2> <p>To install this module, you need to:</p> <ul class="simple"> <li>do nothing special</li> </ul> <p>There are no expected consequences of uninstallation outside of removing all of the groups. Individual attribute values will remain assigned to products.</p> <a name="configuration"></a> <h2>Configuration</h2> <p>To configure this module, you need to:</p> <ul class="simple"> <li>do nothing, no changes are made to existing data and fields and no new dependencies are introduced.</li> </ul> <a name="usage"></a> <h2>Usage</h2> <p>To use this module, you need to:</p> <ul class="simple"> <li>Be a member of the Sales Manager security group or admin for creation, update and removal of groups (same as Variants)</li> <li>Go to Sales -&gt; Configuration -&gt; Product Attribute Group</li> <li>From there you can create Attribute Groups for use in the Variants tab of products by selecting</li> </ul> <p>an attribute and choosing the values belonging to that group. * When adding/removing values to/from an existing group, you must click update variants to populate those changes to all variants using that group. * Groups already assigned to a product template are unable to be changed to a new attribute until removed from those variants.</p> <p>In general this module is designed to work best in a scenario where a a group or group(s) of attributes are commonly reused for a number of templates and are subject to minimal/occasional change. In general, while it is supported, it is not expected in general usage that attribute values will be manually added to templates as well as groups. If using the module in this way it will work however the user experience is not as clean and a wise policy is: either it is groups or no groups.</p> <p>Variants should not be customised as updates will lose those changes. This is Odoo's advice not mine and a sympton of the variant implementation of v8. (In testing, while Odoo states this is the case, certainly product images remained) While additions and removals are supported, the Odoo implementation of variants is to delete/inactivate and recreate them on save of the product template. For this reason additions behave more predictably than removals, which may just be inactivated.</p> <ul class="simple"> <li>The groups act as helper rather than a dictator in the variants screen.</li> <li>It is <em>possible</em> to remove individual values from a product, however as soon as the group is updated these will be readded and is not recommended.</li> <li>Conversely manually adding non-included variants is supported and these will remain after an update.</li> <li>Groups may overlap, and if overlapping groups are added to a template the effect is a Union,</li> </ul> <p>i.e. if A = {1, 3, 5, 7} and B = {1, 2, 4, 6} then A ∪ B = {1, 2, 3, 4, 5, 6, 7} * Removing a group removes its values from the template (provided they are not in an overlapping group). * Discard is your friend. If you see a warning, read it, and if you are unsure discard your changes. * When you add a new value to a group and click Update Variants it will update all of your product templates that use that group.</p> <p>A number of distinct and overlapping groups within the Color attribute have been included in the demo data for experimentation with this functionality.</p> <a name="known-issues-roadmap"></a> <h2>Known issues / Roadmap</h2> <ul class="simple"> <li>Within the code there are some noted github issues relating to the new API. Primarily these are technical in detail</li> </ul> <p>however one in particular, the inability to change the field calling an onchange function, leads to a clumsier than desired user experience when mixing individual attribute values and groups. When deleting an attribute value, from an attribute line in the variant tab of the template screen and it belongs to a variant group, the behaviour <em>should</em> be to change nothing. Currently it removes the attribute and pops a warning. Subsequent updates to the group will readd it to the template.</p> <ul class="simple"> <li>This module will ultimately become part of an app designed to restore the most important functionality of</li> </ul> <p>product_variant_multi* from v7 while remaining sympathetic to the v8 Odoo implementation of variants.</p> <ul> <li><p class="first">Current Modules which will form part of this app are: - <a class="reference external" href="https://github.com/OCA/product-attribute/pull/70/files">https://github.com/OCA/product-attribute/pull/70/files</a></p> <blockquote> <ul class="simple"> <li>product_attribute_code</li> <li>product_attribute_global_item_code</li> </ul> </blockquote> </li> <li><p class="first">Identified remaining features to be implemented</p> </li> </ul> <blockquote> <ul class="simple"> <li>individual variant costs and price history</li> <li>individual variant weights</li> <li>individual variant supplier information</li> <li>search/group/filter by variant</li> <li>bundled product_variant_multi app with configuration options for features</li> <li>automated tests for modules</li> </ul> </blockquote> <ul class="simple"> <li>Possible future features</li> </ul> <blockquote> <ul class="simple"> <li>optional dimensions (very hard)</li> </ul> </blockquote> <a name="bug-tracker"></a> <h2>Bug Tracker</h2> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/product-attribute/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback <a class="reference external" href="https://github.com/OCA/product-attribute/issues/new?body=module:%20product_attribute_group%0Aversion:%208.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">here</a>.</p> <a name="credits"></a> <h2>Credits</h2> <a name="contributors"></a> <h3>Contributors</h3> <ul class="simple"> <li>Graeme Gellatly &lt;<a class="reference external" href="mailto:g&#64;o4sb.com">g&#64;o4sb.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h3>Maintainer</h3> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="http://odoo-community.org">http://odoo-community.org</a>.</p>