Product mapping - Metadata configuration
If you want to transfer a meta property from Bynder to Akeneo, you may choose the best option to fit your taxonomy.
Detailed options
Simple
This option is the main option. It's used to send data from Bynder to Akeneo without any modification.
Mandatory fields for Simple metaproperty
Source : this field must contain the property code of your Bynder meta property. Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for Simple metaproperty
You can select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
Fixed value
When you want to send a specific and fixed value, you can use this type of mapping. As the field is a text, you can put whatever you want in it. It will be sent as is in Akeneo.
Mandatory fields for Fixed values
Value : this field must contain the value you want to put. Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for Fixed values
You can select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
Video preview
When you want to import the link for a video, as Bynder manages different types of video (mp4, webv), you can choose which URL you import.
Mandatory fields for Video preview
Source : this field must contain the property code of your Bynder meta property. Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for video preview
Extension: this field can contain the extension of the video link you want to import into Akeneo. If you leave it empty, the connector will send all the URLs it gets in the API response from Bynder.
You can also select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
Regular Expression
A very powerful mapping type if you want to extract data from text.
Mandatory fields for Regular expression
Source : this field must contain the property code of your Bynder meta property. Regular expression : this part will contain the rule you want to apply to split data. In our example, we split the name into several "groups": product_ref, color_code and type
/(?<product_ref>.*)(?<color_code>.*)(?<type>.*)/
Destination pattern : this part will contain the rule you want to apply to extract data. We use the previous "groups" and utilize them. In this example, we keep product_ref and color_code and concatenate them. We use the group codes between %% to specify it's dynamic values.
%%product_ref%%%%color_code%%
We can also add static values. Here we will concatenate the value with "(AND)" between the 2 groups.
%%product_ref%%(AND)%%color_code%%
Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for Regular Expression
You can select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
Option Sync
The goal of Option Sync is to manage a list in Bynder and create the values in Akeneo if needed. So you don't have to manage the list in the 2 tools.
The configuration is as easy as a simple attribute
Mandatory fields for Option sync
Source : this field must contain the property code of your Bynder meta property. Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for Option Sync
You can select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
External Reference
This type of mapping is really helpful when you want to manage your product identifiers, but they contain special chars. A first job can create in Bynder your SKU or model product codes (even if they contain special chars). See Akeneo to Bynder job In the other jobs, you can use the meta property with this configuration.
A first job can create in Bynder your SKU or model product codes (even if they contain special chars). See Product information
Mandatory fields for External reference
Source : this field must contain the property code of your Bynder meta property. Destination : this field must contain the attribute code of your Asset attribute.
Optional fields for External Reference
You can select the locale and/or channel to enrich. See Generic configuration : Locales and Channels for more information.
Generic configuration : Locales and Channels
For most of the options, you can specify which locale and/or channel you want to enrich.
If your Akeneo asset attribute is localized or scopable, you can decide to send a Bynder metaproperty value to one or many locales or channels.
The values must be the Akeneo codes of your channels or locales. For example, if you use the locale en_US and you want to send the information to this locale, in the field, put en_US.
If you want to enrich many locales (or channels), with the metaproperty value, put your locales separated by a comma (,). Example en_US,en_GB,fr_FR
If you want to enrich all active locales or channels, you can select the corresponding check-box.