Attribute Dictionaries

Use Attribute Dictionaries to maintain controlled value lists used by List Attributes.

An Attribute Dictionary is not a product category. It is a reference list of allowed or suggested values, such as colors, sizes, material grades, finish types, or certification codes.

What the page is for

Open Company Workspace → Data Integration → Attribute Dictionaries when you need to:

  • create a company dictionary for List Attribute values;
  • add or edit dictionary values;
  • browse flat or hierarchical values;
  • import dictionary values from a file;
  • search values by code or label;
  • deactivate outdated values while keeping history.

Create a dictionary

  1. Select the correct company workspace.
  2. Open Data Integration → Attribute Dictionaries.
  3. Fill Dictionary key with a stable key such as steel-grades.
  4. Enter the dictionary name and description.
  5. Add translations if needed.
  6. Create the dictionary.
  7. Add values manually or import values from a file.

The key is permanent integration text. Choose it carefully because imports, exports, and attribute rules can depend on it.

Add or edit values

Select a dictionary, then add or edit values.

Each value has a code and label. A hierarchical dictionary can also have parent-child values. Use hierarchy only when the value structure really has levels.

Import dictionary values

Use the preview/import workflow when you need to load many values.

  1. Select the dictionary.
  2. Upload the file for preview.
  3. Review validation errors.
  4. Import only when the preview is valid. Actualog stores the confirmed upload once, queues it through Data Load, and redirects to the operation status.
  5. The background worker validates and stages bounded batches, synchronizes candidate translations, and activates the complete candidate atomically. You can pause, resume, cancel, or retry the queued operation from Data Load.

The current dictionary stays active until the candidate passes validation and activation. A failed candidate does not partially replace the SQL hierarchy.