Feature Overview
Logical Dependencies lets you define rules that control which Information Values are valid or available depending on what has already been selected in a related Information Code. When a user selects a value for one attribute, the rules you have set up automatically determine which values are permitted for another attribute — preventing invalid combinations and guiding users toward consistent, accurate data entry.
A dependency rule connects two Information Codes. The first code is the driver: the code whose selected value triggers the rule. The second code is the dependent: the code whose permitted values are affected. Each rule specifies an Information Value on the driver code, a test type (Equal, Different from, or Can be), and a Related Information Value on the dependent code. A common pattern is to use Can be rules to list all permitted values for the dependent code when a specific driver value is selected — effectively creating an allowed-values filter.
All rules for a given combination of driver code and driver value must share the same test type. This means you cannot mix Equal and Can be rules for the same driver/value pair. The system enforces this to ensure the rule set is internally consistent.
Logical Dependencies are configured on the Logical Information Value Dependencies page, accessible from the Logical Dependencies action on the Information Code Card. The feature is enabled per Information Code by ticking the Logical Dependencies field on the code card — only codes with this field enabled participate in dependency evaluation.
The rules are evaluated in several different contexts throughout the app. On master data records, the lookup on a dependent code is filtered when a user selects a driver value in the Information Setup. In Specification Search, selecting a value for a driver code automatically filters the available options for dependent codes in the search criteria — so the search itself respects the same rules. On Master Data on Documents, the dependency rules also apply when entering specification values directly on document lines. When the Sales Configurator app is installed, Logical Dependencies additionally extend to configuration on sales and purchase order lines.
Key Facts
| Area | Detail |
|---|---|
| Where to set up | Logical Information Value Dependencies page, accessed via the Logical Dependencies action on the Information Code Card |
| Enable per code | The Logical Dependencies field on the Information Code Card must be enabled |
| Rule structure | Driver Information Code + Driver Information Value → Test Type → Related Information Code + Related Information Value |
| Test types | Equal, Different from, Can be |
| Constraint | All rules for the same driver Code/Value/Related Code combination must use the same test type |
| Evaluation contexts | Information Setup (master data), Specification Search, Master Data on Documents, Sales Configurator order lines |
| Integration points | Information Codes, Information Values, Specification Search, Master Data on Documents, Sales Configurator (optional) |
Getting Started
- Identify the two Information Codes you want to link — the driver code (the one whose value triggers the rule) and the dependent code (the one whose options are affected).
- Open the Information Code Card for the driver code and enable the Logical Dependencies field.
- Do the same for the dependent code.
- Open the Logical Dependencies action from the driver code's card (or navigate directly to Logical Information Value Dependencies).
- Add a new rule line:
- Set Information Code to the driver code.
- Set Information Value to the specific driver value that activates this rule (e.g.
METAL). - Set Related Information Code to the dependent code.
- Set Test type to Can be.
- Set Related Information Value to one of the permitted values for the dependent code (e.g.
POWDER-COAT).
- Add additional lines for the same driver value and dependent code to list all permitted values — each permitted value gets its own rule line with the same test type.
- Repeat for other driver values (e.g. add rules for
FABRICthat permit different values on the dependent code). - Test by opening an item's specification page, selecting the driver value, and verifying that the dependent code's lookup is filtered accordingly.
Related Features
Logical Dependencies builds directly on Information Codes and Information Values — both the driver and dependent codes must have their values defined before rules can be configured. The feature is enabled per code through the Logical Dependencies field on the Information Code Card. Specification Search applies the same dependency rules when users enter search criteria — selecting a value for one code filters what is available for dependent codes in the search form. Master Data on Documents also evaluates the rules when specifications are entered on document lines. If the Sales Configurator app is installed, Logical Dependencies additionally extend to configuration on sales and purchase order lines — see the Sales Configurator documentation for details. Information Values are the building blocks of every rule: the permitted and excluded values must exist before they can be referenced in a dependency rule.
User Stories
US-01: Restrict available surface treatment options based on material type
As a Business Manager
I want to ensure that selecting "Metal" as Material Type only allows metal-compatible surface treatments
So that users cannot select "Dyeing" (a textile process) for a metal product
Setup:
- Enable Logical Dependencies on both the
MATERIAL-TYPEandSURFACE-TREATMENTInformation Code Cards. - Open Logical Dependencies from the
MATERIAL-TYPEcode card. - Add rules: Information Code =
MATERIAL-TYPE, Information Value =METAL, Test type = Can be, Related Information Code =SURFACE-TREATMENT, Related Information Value =POWDER-COAT. - Add a second line with Related Information Value =
ANODISE. - Add a third line with Related Information Value =
GALVANISE. - Add equivalent rules for Information Value =
FABRICwith textile-compatible surface treatments. - Test by setting Material Type on an item and verifying that the Surface Treatment lookup is filtered correctly.
US-02: Prevent a specific combination of attribute values
As a Business Manager
I want to ensure that "Class A1" fire resistance is never combined with "Combustible" material classification
So that contradictory specification combinations cannot be saved
Setup:
- Enable Logical Dependencies on both codes.
- Open Logical Dependencies and add a rule: Information Code =
FIRE-RESISTANCE, Information Value =A1, Test type = Different from, Related Information Code =MATERIAL-CLASS, Related Information Value =COMBUSTIBLE.
Note: Test type Different from means the rule fires when the driver value is selected and excludes the specified related value.
US-03: Allow only one valid value when a specific driver value is selected
As a Business Manager
I want to ensure that selecting "Organic" as Product Origin forces the Certification code to be "EU-Organic"
So that organic products always carry the correct certification
Setup:
- Enable Logical Dependencies on both
PRODUCT-ORIGINandCERTIFICATIONcode cards. - Open Logical Dependencies and add one rule: Information Code =
PRODUCT-ORIGIN, Information Value =ORGANIC, Test type = Can be, Related Information Code =CERTIFICATION, Related Information Value =EU-ORGANIC. - Do not add any other Can be rules for this driver/value combination — with only one permitted value, the lookup will only show that option.
US-04: Review all existing dependency rules for a code
As a IT Manager
I want to see all Logical Dependency rules defined for the "Material Type" code
So that I can verify the rules are complete and correct before training users
Setup:
- Open the Information Code Card for
MATERIAL-TYPEand choose the Logical Dependencies action. - The Logical Information Value Dependencies page opens showing all dependency rules across all Information Codes — it is not pre-filtered to
MATERIAL-TYPE. - Use the standard BC column filter on the Information Code column to filter to
MATERIAL-TYPE. - Review all rules for this code. The list is sorted by Information Code, Information Value, and Value, so all rules for the same driver value appear together.
Note: The Logical Dependencies page always opens unfiltered regardless of which Information Code Card you open it from. Filtering by Information Code must be applied manually each time.
US-05: Extend Logical Dependencies to sales order line validation (with Sales Configurator)
As a Sales Order Processor
I want to ensure that when configuring a product on a sales order line, invalid attribute combinations are blocked
So that orders cannot be placed for products with contradictory specifications
Setup:
- Ensure the Sales Configurator app is installed and enabled.
- Logical Dependencies configured on the master data level are automatically applied during order line configuration — no additional setup is required beyond what is described in the standard Logical Dependencies setup.
Note: This behaviour requires the Sales Configurator app. See the Sales Configurator documentation for full details on how dependencies are enforced during the sales process.
US-06: Use Logical Dependencies to filter available values in Specification Search
As a Sales Order Processor
I want to ensure that when I select "Metal" as Material Type in the Specification Search, the Surface Treatment lookup is automatically filtered to metal-compatible options
So that I can find items by valid attribute combinations without having to know all the rules manually
Setup:
- Ensure Logical Dependencies rules are configured between
MATERIAL-TYPEandSURFACE-TREATMENTas described in US-01. - Open the Specification Search page from the Item List.
- Select
METALin the Material Type search field. - The lookup on Surface Treatment will automatically show only values permitted by the dependency rules.
Note: The dependency evaluation in Specification Search uses the same rules defined on the Logical Information Value Dependencies page. No additional setup is required.
US-07: Apply Logical Dependencies on Master Data on Documents
As a Sales Order Processor
I want to ensure that when entering specification values directly on a sales document line, incompatible value combinations are prevented
So that document-level specification entry follows the same quality rules as master data entry
Setup:
- Ensure Logical Dependencies rules are configured for the relevant Information Codes.
- Open a sales or purchase document that has specification fields visible via the Master Data on Documents feature.
- Select a driver value on a document line — the dependent code's lookup will be filtered automatically according to the dependency rules.
Note: This requires the relevant Information Codes to have Logical Dependencies enabled on their Information Code Cards.
Field Reference
| Field | Where to find it | What it does | Default |
|---|---|---|---|
| Information Code | Logical Information Value Dependencies page | The driver code — the code whose value triggers this rule | — |
| Information Value | Logical Information Value Dependencies page | The specific driver value that activates this rule | — |
| Value | Logical Information Value Dependencies page | Optional value field on the driver entry (used when the entry uses the Value field rather than Information Value) | Blank |
| Related Information Code | Logical Information Value Dependencies page | The dependent code — the code whose permitted values are affected | — |
| Test type | Logical Information Value Dependencies page | The type of rule: Equal, Different from, or Can be | — |
| Related Information Value | Logical Information Value Dependencies page | The value on the dependent code that this rule permits or excludes | — |
| Logical Dependencies (on Information Code Card) | Information Code Card — Logical Dependencies group | Enables this code to participate in Logical Dependency evaluation | Disabled |