How Custom Fields work in Kombiner
Summary
Custom Fields in Kombiner work as a flexible layer that extends your existing data. They are defined once and then used across products, companies, and other areas. In this article, we explain how Custom Fields are structured and how data flows through the system.
What is the structure of Custom Fields?
Custom Fields are built on two parts:
- Field definition
- Field value
The definition controls how the field behaves.
The value is the actual data stored on each item.
You create definitions once, and then reuse them across your data.
Where Custom Fields live
Custom Fields are:
- Created centrally in the system
- Applied to specific areas (products, options, categories, companies, requests)
- Stored as part of each item’s data
This means the same field can be used across many records.
How Custom Fields work
The typical flow:
- You create a Custom Field
- You select where it should apply
- The field appears in the relevant interface
- You add values to individual items
- Kombiner stores the data with each item
The system then makes this data available wherever needed.
How data is used
Once values are added, Custom Fields can be used to:
- Display additional information
- Support internal workflows
- Store imported data from integrations
- Enrich products, companies, and requests
Key concepts
Reusable definitions
A field is created once and reused across multiple items.
Per-item values
Each product, company, or request stores its own value.
Best practices for how Custom Fields work
- Create fields before entering data
- Keep definitions stable once in use
- Avoid renaming fields frequently
- Test fields on a few items before scaling
- Keep structure simple and predictable
Important notes
- Changing a field definition can affect all related data
- Field behavior may vary slightly across different areas
- Not all fields are validated automatically
- Data is always stored within your organization
Common questions
What happens if I change a field name?
It may affect how existing data is displayed or used.
Can I use the same field across multiple items?
Yes, that is the intended use.
Are values shared between items?
No, each item stores its own value.