Hi Michael
It is out - you need to enable it under feature management.
You can read more here:
https://doc.dynamicweb.dev/manual/dynamicweb10/products/managing-products/product-relations.html#dynamic-relations
and here:
https://doc.dynamicweb.dev/manual/dynamicweb10/settings/areas/products/relations/dynamic-relation-groups.html
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.
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.
There are two supported calculation methods:
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.
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.
Hi Michael
First make sure you have the feature, enabled in feature management. But as i read it you already have that .
Secondly, make groups. (and categories.) Categories only in 10.16 and above.
With all that done you should be able to add dynamic relation to the product throught the action menu on the overview screen of the product.
And then once done and saved a new Tab on the overview screen is available. In this example it is material, as i made the relation in a dynamic relation group that is under the material category.
So in regards to where the link is, the it is in that tab. Databasewise they are in EcomDynamicProductRelation.
In terms of data models and groups, then no you do not need to do anything on that. BUT, soon when we release calculation based on the dynamic relations, then it would be beneficial for you to have strucutred the products you link to e.g. material or components, or packaging system or whateter you use, into a data model. Once released a guide will follow..
These are the groups I was mentioning
And after 10.16 dynamic relation groups are created under a dynamic relation category
i will update with images when I'm at a computer.
Thanks Lars, images are visible now :-)
Currently I'm looking into packaging handling, where I for one packing item needs fields like: Item No, Notes, Packaging quantity, Packaging type, Packaging material, Packaging material weight, Packaging waste type and Packaging waste sorting.
I had hoped, that when I manage my packaging items, that I could select the packaging fields and not just an 'Amount'.
Question regarding impact on the Dynamicweb licens, since packaging items are the same as 'products'. So if I have 1.500 products with a total of 10.000 packaging items, what impact will it have on the licens?
Br. Michael Knudsen
Packaging Types
I would define three dynamic relation groups for Primary, Secondary, and Tertiary packaging. These groups can all be placed under a shared category called Packaging.
There are several ways you could model packaging data, depending on the level of detail you want:
Simple Material Setup
Create one product per material type (e.g., Cardboard, Plastic, Glass, Wood, etc.).
Assign a standard unit weight (e.g., 1 gram or another convenient unit).
Example products:
Cardboard (1g)
Plastic (1g)
Glass (1g)
This setup allows you to calculate material usage by simply relating packaging to these base materials. Once the calculation part is released.
Or create packaging products directly (e.g., Cardboard Box, Glass Container).
Use dynamic relations to connect each packaging product to the specific material(s) it is made of.
Or take it all the way to Multi-Level Setup
Create detailed packaging products that consist of multiple elements.
Example: Glass Container incl. Metal Lid and Label.
This product would have dynamic relations to:
Glass Jar
Metal Lid
Paper Label
Each of these elements could then have their own dynamic relations pointing to the base material products (e.g., Glass (1g), Metal (1g), Paper (1g)).
Once again when we have the calculation part released you will be able to calculate the weight of each material.
Depending on the level of complexity you choose, your structure could be organized into:
Material Level (basic materials such as Plastic, Cardboard, Glass)
Element Level (components such as Jar, Lid, Label)
System Level (complete packaging products such as Glass Container incl. Lid and Label)
And then it would end up with something like this, depending on the level you choose do have. Material, Elements or system, as we call them in this example.
License considerations
Increasing the level of detail will naturally increase the number of products in your system.
This also means a higher license footprint, since each material, element, and system component is stored as a product.
As this is a brand new functionality please keep the feedback coming. And if you have a use case we should take a look at together then reach out.
You must be logged in to post in the forum