Skip to content
Product Configurator app iconProduct ConfiguratorRules

Constraint-Based Configuration for Microsoft Dynamics 365 Business Central

An order for a product that cannot be built is worse than no order: it reaches production, stalls, and goes back to the customer. Without constraints, nothing stops a salesperson from combining a component with one it does not fit. Product Configurator prevents incompatible options from being selected together.

Constraints are set up as rules in the Rule Builder or as choice combinations, and they apply while the salesperson configures.

How Constraint-based configuration works in Product Configurator

  1. A product manager identifies combinations that cannot be built, and parts that a choice requires.
  2. The product manager sets up rules or choice combinations for each constraint.
  3. The configuration is tested with valid and invalid combinations.
  4. When a salesperson makes a choice, incompatible choices are hidden or an error explains the conflict.
  5. Only configurations that pass the constraints become items on the order.

Key capabilities

Incompatible choices disappear

A rule can hide an option or a choice once another choice is made. In the demo, choosing a performance keyboard removes the basic mouse option from the list.

Errors for broken combinations

When a combination must never happen, a rule's error action stops the configuration and tells the salesperson why.

Requirements enforced

Rules can require parts when a condition is met. For example, a desk at or above a set length can get its required shelves set automatically, with no way to remove them.

Combinations without rules

For straightforward cases, choice combinations include or exclude components when specific choices are made together.

Same rules everywhere

Constraints run in the BOM Designer and, for show and hide actions, in the bulk editor, so every entry path follows them.

Details that matter on the floor

Fewer orders returned from the floor

Catching an incompatible combination at order entry costs one corrected choice; catching it in production costs a stalled order and a call to the customer.

Enforcement, not reminders

A constraint does not depend on the salesperson reading a note. The choice is unavailable or the configuration cannot finish.

Who uses Constraint-based configuration

Product managers

Define which options cannot be combined and which parts a choice requires.

Manufacturing engineers

Encode build limits so impossible products are never ordered.

Sales representatives

Configure with confidence that an available choice can be built.

Questions about Constraint-based configuration

How do I stop salespeople from choosing options that do not work together?

Set up a rule in Product Configurator that hides the incompatible choice or raises an error, or use choice combinations to exclude components when specific choices are made together.

Can a constraint force a component to be included?

Yes. A rule can set a value when a condition is met, such as adding required shelves above a set length, and the salesperson cannot change it.

Is constraint-based configuration different from the Rule Builder?

It is one of the main uses of the Rule Builder. The Rule Builder also handles defaults, prompts, and messages.

Do constraints apply to bulk configuration too?

Show and hide actions run in the bulk editor, so incompatible options are hidden there as well.

Product Configurator app icon

Part of Product Configurator

Simplify creating BOMs and routing to make quote and order generation more efficient.

Have a question about Constraint-based configuration?

Send us a note and the Product Configurator team will reply by email. Ready to plan a rollout? Contact your Microsoft Partner.

Ask a product question

Product Questions