Style
One style per record: a short code and a name. A style is picked on an item variant, on a pricing line and on the lines of a bill of material.
What it is for
A style is a plain value list. It holds nothing but a code, a name and, on most of them, a Block tick. Its value is that other screens pick it from a list instead of typing it, so the same style is spelt the same way everywhere.
The code must be unique. Saving a second record with the same code is refused.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Style | The short code of the style. | For example RED or XL. Cannot be changed once saved. Required |
| Name | The name shown in lookups and on documents. | A clear name. Required |
| Block | Marks the record as blocked. | Tick to retire it |
How to configure it
Nothing to configure. The Name is kept per language: the name you type is stored for the language you work in and copied to the other languages of the company until someone translates it.
Scenarios
- A garment maker introduces a new style for the season. Create it here first, then add it to the group it belongs to, so it can be picked on the item and its variants.
What it is connected to
- [/screens/products-and-manufacturing/variants-and-attributes/style-group](Style Group) - a group lists several of these values together
- Item - a variant line names its Style
- [/screens/products-and-manufacturing/pricing/pricing-profile](Pricing Profile) - a price line can carry a Style
- [/screens/products-and-manufacturing/manufacturing/bill-of-material](Bill Of Material) - a component line can carry a Style
If something looks wrong
- "... can not be empty" on Save. The code is missing. Type a code.
- "... already exists" on Save. Another record already uses this code. Pick a different code or open the existing one.