Bynder connector bundel

Create the yaml file config/services/bynder_attribute_mappings.yml with the content below.

parameters:

    asset_type_metaproperty_options_mappings: [ ]

    metaproperty_mappings:

        'product_code': ''

        'product_model_code': ''

        'asset_type': ''

        'sort_order': ''

    sortable_asset_type_metaproperty_mappings: []

    enrichment_metaproperty_mappings: []

    enrichment_metaproperty_options_mappings: []

    enrichment_metaproperty_locale_mappings: []

    derivative_to_use: 'original'

    asset_unlink_after_archiving: true

    update_metaproperty_on_empty_only_mappings: []

We will ellaborate on this file in the next chapter to provide the connector with the correct mappings and configuration.

The ‘autoload’-section of the composer.json file should contain the the FileUploader.php path and namespace under ‘files’ and ‘exclude-from-classmap’.

{

  "autoload": {

    "psr-0": {

      "": "src/"

    },

    "files": [

      "src/Bynder/Api/Impl/Upload/FileUploader.php"

    ],

    "psr-4": {

      "Pim\\Upgrade\\": "upgrades/"

    },

    "exclude-from-classmap": [

      "vendor/akeneo/pim-community-dev/src/Kernel.php",

      "vendor/bynder/bynder-php-sdk/src/Bynder/Api/Impl/Upload/FileUploader.php"

    ]

  }

}

Unzip Bynder.zip located in the bundle in the src folder of the project (/src/Bynder/..)

Lastly, make sure you recompile the frontend assets running make front and run a composer dump-autoload to reflect the changes made in the composer.json file.

Config Bynder

We will start off by doing the preparations on the Bynder instance. A few things need to be set up here.

Permanent token

You can create a permanent token by navigating to ‘Advanced settings’ > ‘Portal settings’ > ‘Permanent tokens’ using the cog in the upper right hand side of the application, provided you have the necessary rights to do so.

Clicking ‘Add new’ prompts a form with a Bynder user selection. This would preferably be linked to a dedicated user, since the history/actions will be linked to the selected one. The user should have the following permission active:

Next, you select the access scopes of the token:

After selecting the user, scopes and confirming, a permanent token should be generated (store it somewhere on temporary location as leaving the page will obscure the token) which we can use to add to the credentials in Akeneo.

Metaproperties

A few metaproperties need to be defined/existing to link to a product’s (or model’s) identifier and the related attribute within that product in Akeneo.

First of all, we want a product identifier with the advised configuration as following:

Then we define the same type of metaproperty, but for product model codes:

We want to make sure there is a metaproperty that contains/links to the attribute name that reflects the image attribute name of the product in Akeneo. The following setup would be advised:

There is an optional possibility to map 1 metaproperty option to multiple image attributes, provided they have the same name affixed with a dash and count. (f.e. ‘application’ in bynder => ‘application_1’, ‘application_2’ in Akeneo CE) In that case, an order field needs to be added in Bynder to define the order of the assets that get linked.

Config Akeneo CE

Now that we set up Bynder and we have the permanent token at hand, we can provide mapping and credentials to Akeneo, and have the linking/enrichment jobs scheduled.

Credentials

Adding Bynder credentials to Akeneo CE is done in the UI using the credentials manager provided with the connector. Browse to System > Credentials manager and click on ‘create credential’. Provide the code input with the value ‘bynder’ and select one time key as the type of credential.

When added, you can add the hostname (f.e. induxx-demo.bynder.com) and the permanent token. That’s it!

Mapping

Let’s revisit the bynder_attribute_mappings.yml we added in the installation step. Below we provided some context to the parameter names. What key => value in this configuration is concerned, we are mapping Akeneo (key) to Bynder (value).

Cronjobs

Linking an asset and providing enrichment to an asset is achieved using scheduled commands (cronjob):