Create options in Bynder

This feature is available in the job: Bynder x Akeneo - Send Akeneo product data to Bynder (Bynder Akeneo Connector)

This process allows to automatically create/update meta-property options in Bynder from information present in Akeneo.

This can be product or product model identifiers. It can also be data from other attributes of the data model present in Akeneo.

To avoid sending unnecessary information, only values attached to products are sent to Bynder.

General information

The configuration is split between the Product Model/Product configuration.

• Product Model (top level) refers to the "Common" tab in Akeneo (technically: it's a Product Model without parent)
• Product Model (Middle level) refers to the "Middle" tab (when existing in your family variant) in Akeneo (technically: it's a Product Model with a parent)
• Product variant refers to "Product" in Akeneo when the product is part of a family variant (technically: it's a Product with a parent)
• Simple product refers to "Product" in Akeneo when the product has no parent.

If you want to send your products' identifiers, you must check "Yes" for the option "Send Product identifier". It will show some fields:

• Label attribute - code: put here the code of the attribute you want to use as a label for your product. Generally, it's the title of your product.
• Label attribute - Channel: if your previous attribute is scopable, you must put here the code of the channel you want to ues to get the label.
• Label attribute - Locales: put the codes of the locales you want to send to Bynder
• Bynder property: your destination meta property in Bynder.

If you want you can prefix the label of your product with the identifier between brackets. In that case, you must select yes for the option "Prefix with the label with the product Identifier".

Filters

By default, this concerns all Akeneo products and product models It is possible to filter:

Filters must be integrated into the Akeneo format.

Further information on this subject can be found in the Akeneo documentation

Fallback

Sometimes, you don't have a translation for all of your locales. We've put a "Fallback locales" option. You can put for each locale which other locale value the job can take if the value is not defined in the previous locale.

In this example, if we don't have fr_FR value for our attribute, the connector will take the en_US value.

Other attributes

It works for Product identifiers and Product model codes, but you can also send some other 'Select' or 'Reference Entity' values:

In that case, you must define:

• The code of the attribute
• The channel, if the attribute is scopable
• The locale, if the attribute is localizable
• The default label locale (as Bynder has a "Default value")
• The Reference entity attribute: so you can send another value than the label of your reference entity
• The Bynder property

You can now launch your job to initialize your Bynder meta property options.