DW10 - Product features - Dynamic Relations

Hi Michael

It is out - you need to enable it under feature management.

Next tuesday you get an update on dynamic relations with some updates related to UI (e.g. using tabs) and how units are used.

Next up is calculations - an internal piece of text describing part of the task - for your reference.

Feel free to reach out if you would like a hands-on session and some more insights into the details

Before implementing the UI for displaying calculation results on Dynamic Relations, the underlying data structure must be established in the database.

What a Calculation Considers

A calculation defines how values from dynamic relations should be processed. It is based on the following criteria:

Groups: The target product must belong to one or more specified product groups (e.g. channel group or data model) to be included in the calculation.
Dynamic relation groups: The relation must belong to a specific dynamic relation group within the selected dynamic relation category.
Fields: The fields selected for calculation — only fields of the same type can be calculated together. For example, weight and height cannot be mixed in the same calculation, so if multiple is selected in the setting of the calculation, multiple calculations will be made.

Calculation Methods

There are two supported calculation methods:

1. Sum total for source product

This method calculates the total value of the selected field across all relevant dynamic relations for a source product. It traverses the entire relation tree and aggregates values based on the selected dynamic relation category and group.

Example:

If calculating CO2e emissions and the category is Materials, the system will sum the CO2e values of all target products (e.g., wool, polyester, nylon) that match the selected group (e.g., Material).

Output:

A single numeric result — the total CO2e value for the source product.

2. Sum grouped by target product

This method follows the same filtering logic but returns a grouped result per target product, rather than one total.

Example:

If calculating Weight:

Wool = 20g
Nylon = 30g
Polyester = 15g

Output:

A list of summed values, grouped by target product.

Goal: Have all the results in one database, so we can use it later for specific products in the UI.

here are some of the notes that I did on it. Use it only as what it is NOTES:

Developer forum