Manage Features

Features are used typically for technical attributes or other structure data that describe a product as key and values. Features can be defined by users or Pimics can handle also a standard classification like ETIM, ECl@ss, GS1 and others. Features are used for Data Modeling during the implementation of Pimics. It means you need to identify common attributes for a set of products, put these products under a certain category and set these features on the category level. This helps you to keep data updated and also consistent. Features replace standard attributes from Business Central. Pimics offer more possibilities for how to manage technical data. Pimics offers the possibility to synchronize features back to attributes.

Create Feature

Feature types

Featured can be several types. We recommend setting this type before you use a feature because when you switch the type we validate all values against the new type.

Type Example Description Translations
Numeric Width: 1.234,56 A number in local format No, but value depends on region
Alphanumeric Material: Wood One or more text values Yes, per value
Logical Backrest: Yes Yes/No (or similiar in your language) or eventually technical 0/1 or true/false Yes
Range Alphanumeric Class: A..C From and To Alphanumeric values separate by .. or ; Yes, from and to value
Range Numeric Size range: -1.234,56..1.234,56 From and To Number in local format separate by .. or ; No, but value depends on region
Date Introduce to market: 01.01.1998 Date in local format No, but value depends on region
Document Certificate: ISO-123456 Value can be any document (like PDF) from Pimics. Feature's value is a Description of Document Yes, on documents
Graphic Type of Wood: Maple Value can be any graphic (like JPG, PNG) from Pimics. Feature's value is a Description of Graphic Yes, on graphics
Feature Value is another feature, description of the feature is used as value. It creates separate lines per each value. More details Yes, on features

The field Value shows value as it was written by user, types that can have different meaning in different regions. For example 1.2.2000, is it 1st of February or 2nd of January? Base on region we know it and save it that way. Field Value shows stil 1.2.2000 but field Value Date shows it correcly in another region.

New Feature

Use case (from YAML, Copilot)

  1. Choose the search icon, enter Features, then choose the related link.
  2. Page Features was shown.
  3. Select New to create a new entry.
  4. Page New - Feature Card was shown.
  5. Input Height into the Description
  6. Input Numeric into the Field Type / Field Format
  7. Use field value into the Unit ID field on the New - Feature Card page.
    1. Invoke New on Select.
    2. Page Select - Units was shown.
    3. Input MM into the Unit ID
    4. Input mm into the Unit Shorthand field on the Select - Units page.
    5. Input mm into the Unit Description field on the Select - Units page.
    6. Invoke LookupOk on Select - Units to closed the page
  8. Input Filter into the Default Feature Type field on the New - Feature Card page.

Allowed values for feature

A feature can have a predefined set of allowed values. If there is a predefined list, users can select one or more values from the list, Pimics doesn't allowed to write another value for that feature. The complete list of all values is available on Feature Card. We also know that the set can be slightly different on different Items or Groups, for that reason, you can define different Feature Values Sets

Define Values

  1. Choose the search icon, enter Features, then choose the related link.
  2. Page Features was shown. Select a line and open Feature Card.
  3. Focus on the Description field on the Values part of the Feature Card page.
  4. Input a value into the Description field OR use the Value ID field to select the existing value
    1. You can get the question Similar Value already exists with ID Value ID. Do you wish to use it?
    2. Say Yes on Confirm.
  5. Field Default Value Set gets a new number and the first Value Set has been created, more details about Value Sets.
  6. Repeat step 4 for each value

Polyvalent Features

Polyvalent features are features where a user can select more values for that feature. It is useful for features like Suitable for where you need to select more values.

Before you set a feature as polyvalent feature needs to have predefined set of values

Polyvalent can be set for these feature types:

  • Alphanumeric
  • Numeric
  • Date
  • Document
  • Graphic
  • Feature

Set Polyvalent

  1. Choose the search icon, enter Features, then choose the related link.
  2. Page Features was shown. Select a line and open Feature Card.
  3. Set field Polyvalent in fast tab Allocations to Yes

Business Central Attributes

text

Use case

See also

Title: Manage Features, Author: Pimics Team