One of the data sources Advanced Search uses are attributes. The standard attribute framework has gotten several enhancements which are described in this topic.
When our solution is installed, the standard product attribute values form on products is replaced by a form from HSO. This form offers a clear overview of all linked attributes, their link-source (hierarchy, category and group) and their values, and allows for easier editing of the values. Note that editing the values can only be done in the pane on the right hand side, not in the grid view itself.
This form is only a different way of presenting the data compared to the standard form, it does not introduce additional code or functionality.
Product information management > Setup > Categories and attributes > attributes
Standard Microsoft Dynamics 365 for Finance and Operations does not support any dependency between attributes. However, when for exmaple using both brand and model as attributes, a dependency does usually exist. Let's say we're using cars and there are three car brands: BMW, VW and Volvo. Now each brand has its own car models, but with the standard functionality only, it would be possible to specify invalid combinations of brands and models, such as brand BMW with model Golf (which should only be combined with Volkswagen).
With the Advanced Search functionality it is possible to define parent-child relationships between attributes that will prevent the entry of non-feasible combinations. Note that this is only possible when the attribute types are set up as a Fixed list.
To define a parent-child relationship, the field Parent attribute needs to be filled on the applicable child attribute - this field becomes available on the attribute whenever an attribute is created with an attribute type of fixed list. When a parent is selected, a tab is added to the attribute form where the allowed value combinations can be specified
Example: the attribute Car Model has a parent attribute Car Brand. In the dependent values of the attribute Car model, all feasible combinations can be specified:
Field | Description | Remark |
BMW | 240 |
BMW |
520 |
|
Volkswagen |
Golf |
|
Volkswagen |
Passat |
|
Volvo |
240 |
|
Volvo |
V70 |
|
Volvo |
V90 |
Note
Product information management > Setup > Categories and attributes > Attribute groups
Attributes can be sorted within the attribute group either alphabetically or manually.
The default value for the Attribute sorting field on an attribute group is alphabetically, however, if a different sequence is desired this setting can be switched to manual. This activates the move buttons Top, Up, Down and Bottom on the attributes tab within the attribute group and have been added to be able to sort the attributes into the desired sequence.
This sorting will influence the way the attributes are shown in the compare attributes form and other (product) attribute value forms.
Note
Product information management > Setup > Categories and attributes > attributes
There are two additional fields on the attribute to control filter behavior:
Field | Description | Remark |
Not filterable | When this setting is activated, the values from this attribute will be searchable via text search, but they will not be created as separate filters | This is useful for attributes where all or most values are different/unique which would create a large amount of filters with little use, such as item number, description, length, weight etc. (Note that for attributes such as length and weight Value ranges offer a differenr solution approach.) |
Value range |
Select a Value range for this attribute. It is only possible to select a filter range for the supported base types (integer, decimal, date/time). |
Only filter ranges with the same base type as the current attribute type can be used. Filter ranges can group attribute values together when creating the filter for it. For more information see Value ranges. |
The MS standard attribute framework only allows 1 value per attribute for a product. But in some scenario's being able to pick multiple values for the same attribute can make sense: think for example of languages in which the product documentation is available, or a list of certificates out of which multiple could apply to the product.
Multi-value attributes only work for fixed-list type attributes. On attribute types that have the 'Fixed list' button activated, the 'Allow multi-value' becomes available to activate as well on the attribute type.
Any attribute making use of an Attribute type with a fixed list and the Allow multi-value setting activated will allow for multiple values to be selected from the list of valid values.