Back

How Logical dependencies are displayed in the user interfase on Sales Lines

Logical dependencies to substitute Components based on Master Data Information
Video 2/2
Play
Close
  • Helpful
  • Not helpful
  • Needs update
  • Technical error
An intermediate video requires some previous experience with Business Central, but it is still easily accessible to most people. Intermediate Watch the "basic" videos to take the tour of the main processes of Business Central. This is the basic, need-to-use functionality. The Basics This video includes functionality from the app "Sales Configurator" which is available at Microsoft AppSource. Click to visit AppSource. Sales Configurator

Playlists  Manage

Log in to create a playlist or see your existing playlists.

Presenter: Sune Lohse, Chief Strategy Officer

The configurator in Microsoft Dynamics supports logical dependencies, which limit the choices a user can make when entering data on a configuration line. When you select one value, the configurator automatically narrows down the options available for the next field, so you can only pick combinations that actually make sense.

For example, if you select a specific bike type, the configurator only offers the gear options that are valid for that bike. This prevents invalid combinations and makes data entry faster and more reliable.

How logical dependencies work in the configurator

The functionality for logical dependencies applies directly to the configurator. When you open the configuration window and select a template to start entering data, the dependencies are active right away.

Say a customer wants a 20-gear bike. When you enter the bike type, you may see that only one selection is available, because the logical dependency works from this view and filters out everything that does not fit.

If you had not selected any gear requirement, you could choose between all the different kinds of bikes. But once you select a specific bike, for instance the Colibri bike, the configurator shows that only certain gear options are valid for that model.

Defining dependencies that limit the selection

This is how you define dependencies that limit the selections available on a configuration line. You set up rules so that choosing one value restricts the options for related fields. The result is a guided entry process where users only see and select valid combinations, reducing the risk of configuration errors.

Q&A

What are logical dependencies in the configurator?

Logical dependencies are rules that limit the selections available on a configuration line. When you choose one value, the configurator narrows the options for related fields so you can only select valid combinations.

Where do logical dependencies apply?

They apply to the configurator. They are active when you open the configuration window, select a template, and start entering data.

Can you give an example of how it works?

If you select a specific bike, such as the Colibri bike, the configurator only shows the gear options that are valid for that model. If you have not yet selected a bike, you can choose from all the different bike types.

475780087-ubiun1CVFqE-ENG20090638