What is the difference between field definitions and values?

Summary

Custom Fields in Kombiner are built using two parts: field definitions and field values. Understanding the difference is key to using them correctly. This helps you manage your data structure and avoid issues when editing or scaling your setup.

What is the difference between field definitions and values?

In Kombiner, a Custom Field is not just a single input. It is a combination of:

• A field definition (the structure)
• A field value (the data)

The definition is created once and reused across your organization.
The value is added individually on each product, company, or request.

Example:

You create a field called “Material”

• Definition → “Material” (text field applied to products)
• Value → “Stainless steel” (on Product A)
• Value → “Aluminum” (on Product B)

When should I think about definitions vs values?

You should understand this difference when:

• You are creating new Custom Fields
• You are editing or renaming existing fields
• You are structuring data across many items
• You are importing data from external systems
• You want consistent data across your organization

How definitions and values work

The typical flow:

1. You create a field definition
2. Kombiner makes the field available in the selected area
3. You add values to individual items
4. Each item stores its own value
5. The definition connects all values across items

This allows one field to be reused across many records.

Key concepts

Field definition

Defines:

• Name
• Data type
• Where it applies

It is shared across all items in your organization.

Field value

This is:

• The actual data entered
• Stored per item

Each product, company, or request has its own value.

Best practices for definitions and values

• Create definitions before entering large amounts of data
• Use consistent naming for definitions
• Avoid renaming fields after they are in use
• Reuse definitions instead of creating duplicates
• Test fields before applying them widely

Important notes

• Changing a field definition affects all related values
• Renaming a field can impact how data is displayed or used
• Deleting a definition may remove associated values
• Values are always stored per item, not globally
• Definitions are shared within your organization only

Common questions

Can I change a field after adding values?

Yes, but changes may affect all items using that field.

Are values shared between products?

No, each product stores its own value.

What happens if I delete a field definition?

All associated values may be removed or become unavailable.