Logical dependencies in Business Central let you control which master data values are valid based on what the user has already selected. When you set up a dependency between two pieces of master data, the system filters the second value list so it only shows the options that fit the first selection. This works on the basic tables like items, vendors, customers, and serial numbers, and it also works on document lines for sales orders and purchase orders.
The benefit is fewer wrong entries. A user can only pick combinations that actually make sense, because the list narrows down automatically as soon as a related value is chosen.
Logical dependencies apply to basic tables and document lines
Logical dependencies work in two places. First, on the basic tables where you keep your core information: items, vendors, customers, serial numbers, and anywhere else master data lives. Second, on the master data attached to document lines. If you have a sales order or a purchase order and you enter master data information directly on the line, the same dependency logic applies there too.
This means the filtering follows your data wherever it appears. You set up the dependency once, and it controls the value lists both on the master records themselves and on the documents that reference them.
How the filtering works on a document line
Take a sales order line where you enter master data information. In one example, a line has a gear value but no bike type attached. When you drill down on the gear, for instance a Nexus 7 gear, you see the full value list of every gear option available.
Now set up the bike type as the controlling information value. Once the gear depends on the bike type, the gear list shortens. If you select the City bike as the bike type and then look up the Nexus 7 gear, the list is reduced to only the values that are valid for that selection. You expect to see just the two relevant options instead of every gear in the system.
The dependency runs in the direction you define. In this case the bike type controls which gear values are available, so choosing the bike type first narrows down what you can pick for the gear.
Setting up logical dependencies for cleaner data entry
To get the benefit, define which master data value depends on which other value. From that point on, the system handles the filtering automatically. Wherever that master data shows up, whether on the records themselves or on sales and purchase documents, the value lists respect the dependency and only present valid combinations.
This is a practical way to reduce data entry errors. Instead of relying on the user to know which gear belongs to which bike type, the list does the work and limits the choices to what is correct.
Q&A
Where do logical dependencies apply in Business Central?
They apply to the basic tables such as items, vendors, customers, and serial numbers, and to master data attached to document lines on sales orders and purchase orders.
What happens when I drill down on a value with a dependency set up?
The value list is filtered. You only see the options that are valid based on the related value you have already selected. For example, selecting a specific bike type shortens the list of available gear values to just the matching ones.
What is the benefit of using logical dependencies?
You prevent invalid combinations during data entry. The system narrows the value list automatically, so users can only pick values that fit the selection they have already made.