Export product properties

Introduction

In this part we will synchronize Contentserv attributes as Shopware properties – to be exact as property values. Shopware strictly differs between the Shopware properties and it’s property values. The properties must be maintained in Shopware first for the connector to be able to fill them with their according values.

Don’t forget to import them into your station values once you created all on the Shopware side.

Configuration

Using attribute references (Recommended)

Contentserv Maintenance

If the properties of your products are the same with the variant building attributes, you can re-use the maintained attribute reference for them as well. Otherwise, a new attribute reference should be created which will represent the attributes a product will have on the Shopware side.

Create the attribute reference product attribute.

Activate the selection of multiple attributes.

Leave the language-dependency unchecked.

For a far easier maintenance, we would recommend using the inheritance by parent elements. For example: If all T-shirts have textile it can be mapped at their common parent node.

When mapping the station values using this method, we map a Contentserv attribute directly to the Shopware 6 property. Therefore for the station value type, select “Pdmarticle attribute”.

Map each attribute to each property.

Exporting the product properties to Shopware

Go to the datamap and enable properties, and map the property selector attribute as the source for that row.

Open the configuration for properties.

Find the attribute which contains your width value and map it. (same as with variants)

Map this attribute to width within the properties configuration.

Click the cogwheel and open the sub configuration.

Save.

Click the red cogwheel to enter the sub sub configuration.

Change object type to property

Run your job.

Your property should now be available.

Re-validation: Am I finished with my configuration?

So, you feel like you followed every step but still the connector does not spit it out. In this case here’s a quick check where the problem lies 90% of the time.

1. Is the attribute maintained in the Shopware properties attribute reference in the PIM product?
2. Is the attribute set in the station values?
3. Is the attribute configured in the datamap? The variants need their own property datamap row. You have to copy your newest changes to them as well.

If it’s not one of those, you might have discovered a bug. In that case you can create a ticket in our Redmine system.

Was this article helpful?

0 0

How can we improve this article?

Please submit the reason for your vote so that we can improve the article.

Name

Email

Submit