When you work with master data information in Business Central, you need to understand three distinct layers: the information code, the information value, and the information setup that ties everything together. Each layer plays a different role, and knowing how they fit together is what lets you build clean, reusable master data.
The information code is the top level. It works like a generic field you add, such as “product type” or “wheel diameter”.
The information value is a dropdown tied to a specific information code. It is not related to any specific item, customer, vendor, or order. It only lists the possible values that belong to that code.
You attach codes and values to specific records (items, customers, vendors, and so on) in the setup layer. This is where you connect a generic structure to your actual master data.
Use the value field for entries that are specific to each record, like heights, sizes, or RAL colors. You can apply validation to the value field, for example forcing a decimal or a date, so the system checks the data type when you enter it.
The three layers of master data information
When you work with master data information, it helps to separate the structure into three layers.
At the top you have the information code. This is a generic value, similar to adding a field. Examples are “product type”, “tire type”, or “wheel diameter”.
Below that sits the information value. This is a dropdown derived from the information code. It is not tied to any specific item, customer, vendor, or order. It simply holds the list of possible values that belong to a given code.
The information code and the information value are defined separately from each other. Once they exist, you bring them together in the setup layer, where you select them per item, per customer, or per vendor, depending on where you work with master data information.
How the layers work together: item 1162
Take item number 1162 as an example. In the information setup for this item, there are three different entries.
- The first line uses the information code product type, with the value selected from a dropdown (the information value). There is no separate value entered, because you only want to pick from the dropdown.
- The second line uses the information code tire type, also selected from a dropdown of information values.
- The third line uses the information code wheel diameter, with the information value inch, and then a value that is specific to item 1162.
For the first two lines, the description comes straight from the information value in the middle layer. That keeps it generic and consistent across records.
When to use the value field
The third line shows why the value field exists. For the wheel diameter, you do not want the value to be a generic dropdown from the information value list, because that would create a long and unwieldy dropdown. Instead, the value is tied to each individual item, customer, or vendor, so you can state a specific number.
This is the right place for data such as heights, sizes, or specific colors like RAL colors. You enter the value field per entry in the information entry table, so it stays specific to that record.
Validation on the value field
The value field can also carry a validation type, which gives you an extra check on your data. If the validation type is a date, Business Central checks that the entry is a date. If it is a decimal field, it checks for a decimal.
For item 1162, the wheel diameter value is set up as a decimal field. If you try to enter something that cannot be interpreted as a decimal, Business Central tells you it is not possible and asks for a decimal value. Enter 27, for example, and it accepts the entry.
The product type, by contrast, has no validation type defined in the setup, so its value can be anything.
Summary of the structure
The information code is the top level. The information value is a drill-down on the information code, and the two are defined separately. You then select them per item, per customer, or per vendor, wherever you work with master data information.
The value field lets you apply logic and validation to record-specific data. The description field defaults from the other fields, but you can override it and enter whatever you need.
Q&A
What is the difference between the information code and the information value?
The information code is the top level and works like a generic field you add, such as “product type” or “wheel diameter”. The information value is a dropdown derived from that code, holding the list of possible values. The two are defined separately, and neither is tied to a specific item, customer, or vendor on its own.
When should I use the value field instead of an information value dropdown?
Use the value field when the data is specific to each record and would otherwise create a long, unwieldy dropdown. Typical examples are heights, sizes, and specific colors like RAL colors. The value field is entered per entry in the information entry table.
Can I validate what users enter in the value field?
Yes. You can assign a validation type to the value field. If it is set to a date, Business Central checks the entry is a date. If it is set to a decimal field, it checks for a decimal and rejects anything that cannot be interpreted as one. If no validation type is defined, the value can be anything.
Where does the description in a master data information entry come from?
The description defaults from the other fields, typically the information value. You can keep the default or enter your own text.