Developer forum

Hi Adrian

I am not sure what you are trying to acheive. With the related products . 
Maybe you can specify or give an example. 

In Swift we support related products, in different related groups.

But if you need to create a related product section "Similar products" you can create a new row with related product paragraph and point that to a specific service page,
where you can override the product view model parameters if needed based some of your criterias.
But i guess i need an actual example to guide you further.

Best regards

Jennifer

Example of what i mean :)

• You can create your design using product components
• and use the design on the Product component slider
• Select Advanced / Custom
• And point to a Service page , where you define/overrride som specifc parameters

https://doc.dynamicweb.com/swift/setup-project/ecommerce-design/product-components#sideNavTitle1-3-14

Hi Jennifer,

My specific use case is that I want to list a specific Related Group using the Component Slider.

In the version I started with, I can use the Product Slider (not component slider) but that one will create a group for every related group I have defined.

The Product Component Slider does not even have the option to use Related Products:

Maybe the setup for my use case is a bit different?

Thank you,

Adrian

Hi Adrian 

Yes the Product Component Slider is missing the Related producs option. I have a task item for that in the queue.

And yes with Product Slider it wil divide the products into the different related groups that are specified.
And it is not possible to select one or multiple related groups out to show.  (But this is a request i have heard before, which we can look into) . 

The only thing that i can think of is Creating a new related group called Similar products, but you will still run into the issue that it will show all related groups if they are added on the product
 

Hi Jennifer,

Thank you for the clarification.

I believe that a "Related group selector" would solve the issue.
We have solved it this way:

Maybe it makes sense for the user to have the option to decide which relation groups should be displayed instead of displaying all.

Thank you,

Adrian