The configurator in the Master Data Information app lets you guide product selection using logical dependencies. When you pick one parameter, the system automatically narrows down the valid options for the other parameters. This works in both directions, so it does not matter whether the customer starts with the bike type or the number of gears.
You set up the rules in the Configuration Dependency List. Here you define which combinations are valid, for example that a city bike cannot have 20 or 21 gears, while a mountain bike can.
The feature helps you handle situations where a customer describes what they want but you do not yet know which specific item to produce or sell. You make the selections based on the customer’s requirements, then search for items that match.
How logical dependencies work in the configurator
When you enter a sales order line and you do not yet know which item to produce, the configurator gives you a way to search for items. You can pre-fill the selection with a template, so you start from a set of default information rather than from scratch.
The interesting part is how the dependencies between parameters behave. Say you have a list of 8 to 10 bike types and a list of gears with around 7 or 8 options, including gears with 20 and 21 gears.
If you select a bike type first, for instance a city bike, and then open the gear list, the list is now shorter. The logical dependencies have removed the gears that are not valid for a city bike, so you no longer see the 20 or 21 gear options.
You use this window to make the selections the customer asks for. When you are done, you search for items that fit the selection. In some cases there are no items matching the exact combination. In others you find a partial match, for example a city bike that matches on one criteria.
The selection works in both directions
The dependencies are not a one-way flow. You do not have to start with the bike type.
If you start by selecting the gear, for instance a 20-gear bike, and then open the bike type list, the selection narrows there too. You only see the bike types that are valid for a 20-gear, which in this case is the mountain bike.
This means the customer can lead with whichever parameter they care about most. If they start by saying they want a 20-gear bike, it is easy to select the other parameters around that. If they start by saying they want a mountain bike, you can pick the gear based on that choice.
Setting up the Configuration Dependency List
You set up these rules in the Configuration Dependency List. There you define the valid combinations, for example:
- If the bike type is a city bike, the gear has to be different from 20 gear.
- If the bike type is a mountain bike, the gear can only be a specific set of options.
These rules form a logical configuration flow. There is a dedicated video on this in the Master Data Information collection that walks through the setup in detail.
Q&A
What are logical dependencies in the configurator?
Logical dependencies are rules that control which parameter combinations are valid. When you select one parameter, the configurator automatically narrows the available options for the other parameters based on these rules.
Where do I set up logical dependencies?
You set them up in the Configuration Dependency List in the Master Data Information app. There you define which combinations are allowed, such as restricting which gears are available for a given bike type.
Does the selection only work in one direction?
No. The dependencies work both ways. You can start by selecting the bike type and then narrow the gear options, or start with the gear and narrow the bike types. The customer can lead with whichever parameter matters most to them.
What happens if no item matches my selection?
When you search for items that fit the selection, the configurator shows you the matches. If no item matches the exact combination, you see that no items exist for that scenario. In some cases you find a partial match that fits one of the criteria.