NexCommand AINexCom Knowledge Base
Field reference

Item Variant Settings

How to use Item Variant Settings in Items & Categories: access, working steps, fields, related records and troubleshooting.

Supply ChainUpdated 12 October 2026Configuration-aware guidance
Open Item Variant Settings ↗Module guide

Purpose and access

Create items with their identifiers, units and applicable stock settings. Choose classification through the category hierarchy. Keep UNSPSC item groups and supplier categories consistent with the products and services being traded.

This page is a settings page in Supply Chain → Items & Categories. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Review the current settings or existing records and prepare the information needed for the change.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open Item Variant Settings from Supply Chain → Items & Categories, or use ERP Search.
  2. Review the existing configuration before editing.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
  5. Save the record and address validation messages. Reload and verify the saved values and relationships.
  6. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
Do not update variants on savedo_not_update_variantsCheck
Optional		Fields will be copied over only at time of creation.
Allow Rename Attribute Valueallow_rename_attribute_valueCheck
Optional		Rename Attribute Value in Item Attribute.
Allow Variant UOM to be different from Template UOMallow_different_uomCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
FieldsfieldsTable
Optional		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Variant Field

Child tables

Fields — child-row fields
FieldType / behaviorHow to use it
Field Namefield_nameAutocomplete
Required		Complete the value according to the field label and the record’s validation rules.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.
Was this useful?